Fail on http errors

[nzlosh]

This PR updates the following:

• actions regenerated against netbox api 4.3.
• removed masking netbox http return codes and messages
• added parameter fail_non_2xx so actions will return failed instead of succeeded on non 2xx http return codes.

[abhi1693]

I'm not in favour of hard coded 200 and 300 status code checks when the parameter is for 2xx checks. It's a bit misleading for the user. Moreover, due to different configurations or - actions, an http code of a different value may be received. Assuming it's 201, which must still be accepted, the code will raise an error leading to more issues.

[nzlosh]

The range function generates a list from 200 to 299.

        if fail_non_2xx:
            action_succeeded = result.get("status") in range(200, 300)

For an HTTP status code of 201 Created the action will be successful while a 403 Forbidden will be failure. In the previous version of the code, the action was always successful even when 403 Forbidden was returned.

I understand in some use cases this behaviour is desirable because the action did succeed in communicating with the netbox API despite access refused. In other use cases the action success is based on fetching the data to proceed with processing the workflow and a failure to fetch the data is considered an action failure.

The PR is written to default to the same behaviour as the previous version while allowing users to choose which behaviour fits their use case.