chore: Mark user-info-fetcher as non-experimental (#752)

* chore: Mark user-info-fetcher as non-experimental

* changelog

Author: sbernauer

CHANGELOG.md

@@ -14,8 +14,10 @@ All notable changes to this project will be documented in this file.
 - BREAKING: The per-rolegroup services now only serves the HTTP port and has a `-headless` suffix to better indicate their
   purpose and to be consistent with other operators ([#748]).
 - BREAKING: The per-role server service is now prefixed with `-server` to be consistent with other operators ([#748]).
+- The User info fetcher is no longer an experimental feature ([#752]).
 
 [#748]: https://github.com/stackabletech/opa-operator/pull/748
+[#752]: https://github.com/stackabletech/opa-operator/pull/752
 
 ## [25.7.0] - 2025-07-23
 

docs/modules/opa/pages/usage-guide/user-info-fetcher.adoc

@@ -1,7 +1,5 @@
 = User info fetcher
-:description: Experimental User Info Fetcher for OPA retrieves data from backends like Keycloak. Integrate extra user details into Rego rules for enhanced policy management.
-
-WARNING: This feature is experimental, and subject to change.
+:description: User Info Fetcher for OPA retrieves data from backends like Keycloak. Integrate extra user details into Rego rules for enhanced policy management.
 
 The _User info fetcher_ allows for additional information to be obtained from the configured backend (for example, Keycloak).
 You can then write Rego rules for OpenPolicyAgent which make an HTTP request to the User info fetcher and make use of the additional information returned for the username or user id.