docs: Use a specific rather than a generic message for documenting the authentication provider

[iansergeant42]

Description

This change makes it easier to document the ZWEAM105 message by linking it specifically to documenting which authentication provider is being used rather than being a generic message.

Linked to # (issue)
Part of the # (epic)

Type of change

Please delete options that are not relevant.

• docs: Change in a documentation
• refactor: Refactor the code

Checklist:

• My code follows the style guidelines of this project
• PR title conforms to commit message guideline ## Commit Message Structure Guideline
• I have commented my code, particularly in hard-to-understand areas. In JS I did provide JSDoc
• 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
• The java tests in the area I was working on leverage @nested annotations
• Any dependent changes have been merged and published in downstream modules

For more details about how should the code look like read the Contributing guideline

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud