docs: Remove outdated annotations

Author: siegfriedweber

docs/modules/opensearch/pages/usage-guide/monitoring.adoc

@@ -32,8 +32,6 @@ apiVersion: v1
 kind: ConfigMap
 metadata:
   name: custom-opensearch-security-config
-  annotations:
-    restarter.stackable.tech/ignore: "true"
 data:
   config.yml: |
     ---

docs/modules/opensearch/pages/usage-guide/security.adoc

@@ -144,30 +144,7 @@ spec:
 
 If this role group is not defined, it will be created by the operator.
 
-[IMPORTANT]
-====
 Settings managed by the operator are hot-reloaded when changed, i.e. without pod restarts.
-However, if those settings are provided via ConfigMap or Secret, updates will normally trigger a restart.
-To prevent that restart, add the following annotation:
-
-[source,yaml]
-----
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: security-config
-  annotations:
-    restarter.stackable.tech/ignore: "true"
----
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: security-config
-  annotations:
-    restarter.stackable.tech/ignore: "true"
-----
-====
 
 == TLS
 

docs/modules/opensearch/pages/usage-guide/upgrade.adoc

@@ -10,25 +10,6 @@ If you used this name for your custom security configuration, then you must rena
 Otherwise the operator will override it.
 
 The operator now supports hot-reloading of security settings.
-If those settings are provided via ConfigMap or Secret, then the annotation `restarter.stackable.tech/ignore: "true"` should be added to avoid restarts triggered by the restart controller:
-
-[source,yaml]
-----
----
-apiVersion: v1
-kind: Secret
-metadata:
-  name: security-config
-  annotations:
-    restarter.stackable.tech/ignore: "true"
----
-apiVersion: v1
-kind: ConfigMap
-metadata:
-  name: security-config
-  annotations:
-    restarter.stackable.tech/ignore: "true"
-----
 
 == Upgrade from SDP 25.11 to 26.3