Improve gateway error messages

[mjamescompton]

Summary

Extend the error mapping for claim related errors regarding The Things Indoor Gateway Pro.

Changes

• Update getClaimGatewayErrorMessage

Testing

Steps

To test this you need to setup The Things Indoor Gateway Pro to a selection of states. This can only be done internally by the team.

Configure the The Things Indoor Gateway Pro billing to be suspended, detached, not set. Use the gateway owner token.

Error messages

subscriptionDetached: `The gateway billing is detached. Open the Gateway Status page by scanning the QR code on the gateway.`,
subscriptionSuspended: `Your gateway billing is suspended. Open the Gateway Status page by scanning the QR code on the gateway.`,
subscriptionUnknown: `The gateway billing is not set up yet. Open the Gateway Status page by scanning the QR code on the gateway.`,

Configure the The Things Indoor Gateway Pro billing to be not set. Create a fleet with no slots. Use the gateway owner token to register gateway.

Error message

There are no available Gateway Licenses for this gateway. Open the Gateway Status page by scanning the QR code on the gateway.

Configure the The Things Indoor Gateway Pro to be attached to a Gateway License within a fleet, create a second Gateway Fleet and use the empty fleets owner token.

Error message

The gateway EUI matches a Gateway License, but the fleet ID does not match. Open the Gateway Status page by scanning the QR code on the gateway.

Go to register gateway in the console. Using the provided gateway EUIs and owner token for each state and check to see the correct error messages.

Results

Regressions

Before updates to the Gateway Controller the raw error messages from the stack will be shown.

Notes for Reviewers

...

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Testing: The steps/process to test this feature are clearly explained including testing for regressions.
• Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.