[DXCDT-77] Fix attack protection resource for psaas tenants

[sergiught]

Description

This PR accounts for PSAAS environments that don't have the Stage property set on the SuspiciousIPThrottling setting.

We also improving error handling and making it much more robust within the attack_protection resource.

Fixes: #85.

Checklist

Note: Checklist required to be completed before a PR is considered to be reviewable.

Auth0 Code of Conduct

• I have read and agreed to the terms within the Auth0 Code of Conduct

Auth0 General Contribution Guidelines

• I have read the Auth0 General Contribution Guidelines

Changes include test coverage?

• Yes
• Not needed

Does the description provide the correct amount of context?

• Yes, the description provides enough context for the reviewer to understand what these changes accomplish

Have you updated the documentation?

• Yes, I've updated the appropriate docs
• Not needed

Is this code ready for production?

• Yes, all code changes are intentional and no debugging calls are left over

[willvedd]

Appreciate that you've jumped on a fix for this, but can we take a moment to learn the facts? There is a lot of fear and uncertainty around the API which sours the code. Instead of hastily applying a code patch, can we instead identify what the PSaaS API actually returns?

In addition to learning the full scope of this issue, can we also understand if this is something that we actually want to address with code? Perhaps we can identify workarounds or work with the relevant product teams to understand what a more holistic fix looks like. Given that Layer0 is on the horizon, we may be able to wait.

[willvedd]

Great work, thanks for walking me through this!