remove try auth mode

[pgayvallet]

Summary

Follow-up of #92784 given #92784 (comment)

• Remove the authRequired: try auth mode
• Use HAPI's try mode instead of optional when authRequired is optional

Checklist

• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: ec79c02
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💔 Build #112431 failed 73fa489
• 💔 Build #112428 failed 1c3d491

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[joshdover]

Just to be sure I followed along here correctly:

• We used to have required and optional where optional would return an error for invalid creds
• We added try which would not return an error for invalid creds
• We're now replacing optional with try's behavior and removing try. So now invalid creds are treated the same as no creds on optional routes.

Sound right?

[pgayvallet]

@joshdover that's right.

We confirmed with the security team that they were ok using (HAPI's) try instead of optional for their routes.

Note that the only reason why we need to use HAPI's try (treat invalid creds as no cred) is the way the FTR tests are deleting users before accessing the logout page (which cause failures because the /bootstrap.js endpoint throws a 403 in that case when accessing the page), but fixing that in FTR would be so impactful that we decided to just switch to try instead.