docs(docs): Update auth token to use new catalyst id

[stevenj]

Description

This changed the auth token to align with consistent use of the new catalyst-id.
It will help reduce the amount of alternative means of achieving the same outcome.
All RBAC registrations can reliably be found using the catalyst ID.

Breaking Changes

The ID is completely different, however the old auth token has never been deployed into production.
Its also similar in content, but different in formatting.

Related PR

• Depends on: feat(rust): Upgrade the Catalyst Key Id to be a more general Catalyst ID which can be used both as a Key ID and a registration ID. catalyst-libs#159

Please confirm the following checks

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream module

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 392/392}$ | ${\color{red}Fail: 0/392}$ |

[github-actions]

✅ Test Report | ${\color{lightgreen}Pass: 392/392}$ | ${\color{red}Fail: 0/392}$ |

[nathanbogale]

LGTM

[neil-iohk]

Line 20 suggested improvement:

It consists of an Authentication Header attached to every authenticated request, and an encoded signed.

Replace with

The authentication token consists of two parts:

1. An Authentication Header that must be attached to every authenticated request
2. An encoded signature that verifies the token's authenticity