Update Keycloak examples to Keycloak version 20.0.

[guicassolato]

• Update all Keycloak examples and e2e tests to work with Keycloak version 20.0
• Add some screenshots to a user guide that uses the new Keycloak version

Depends on Kuadrant/authorino-examples#35.

The following user guides are affected and have been re-tested:

• OpenID Connect Discovery and authentication with JWTs
• OAuth 2.0 token introspection (RFC 7662)
• Token normalization
• Edge Authentication Architecture (EAA)
• OpenID Connect UserInfo
• Resource-level authorization with User-Managed Access (UMA) resource registry
• Simple pattern-matching authorization policies
• OpenID Connect (OIDC) and Role-Based Access Control (RBAC) with Authorino and Keycloak
• Authorization with Keycloak Authorization Services
• Redirecting to a login page
• Mixing Envoy built-in filter for auth and Authorino
• Using Authorino as ValidatingWebhook service

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	Secret	Commit	Filename
8184017	Keycloak Api Keys	91d587e	docs/user-guides/observability.md	View secret
8184017	Keycloak Api Keys	91d587e	docs/user-guides/observability.md	View secret
8184017	Keycloak Api Keys	91d587e	docs/user-guides/observability.md	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>