Add disableSubPathExpr: true to plugins yaml (#701)

Cherry-picked #699

Author: renetapopova

modules/ROOT/pages/kubernetes/configuration.adoc

@@ -558,7 +558,7 @@ Some examples of possible Neo4j configurations::
 
 [[configure-neo4j-name]]
 == Set neo4j.name parameter
-Starting from Neo4j 5.0.0, standalone servers and cluster servers have no distinction. 
+Starting from Neo4j 5.0.0, standalone servers and cluster servers have no distinction.
 This means a standalone server can be upgraded to a cluster by adding more servers.
 Therefore, the `neo4j.name` parameter, which value links together servers in a cluster, is mandatory, and the installation will fail if it is not specified.
 `neo4j.name` must be unique within a namespace.
@@ -826,7 +826,7 @@ ssl:
       sources: [ ]
 ----
 
-Now you are ready to <<deploy-neo4j-cluster-ssl, deploy the Neo4j cluster>> using the configured _ssl-values.yaml_ file and the Neo4j Helm charts.  
+Now you are ready to <<deploy-neo4j-cluster-ssl, deploy the Neo4j cluster>> using the configured _ssl-values.yaml_ file and the Neo4j Helm charts.
 
 === Configure an SSL policy using a `generic` Kubernetes secret
 
@@ -842,7 +842,7 @@ For more information, see xref:kubernetes/quickstart-cluster/prerequisites.adoc[
 +
 [source, shell]
 ----
-cat public.crt| base64 
+cat public.crt| base64
 ----
 +
 [source, shell]
@@ -932,7 +932,7 @@ ssl:
       sources: [ ]
 ----
 
-Now you are ready to deploy the Neo4j cluster using the _ssl-values.yaml_ file and the Neo4j Helm charts. 
+Now you are ready to deploy the Neo4j cluster using the _ssl-values.yaml_ file and the Neo4j Helm charts.
 
 [[deploy-neo4j-cluster-ssl]]
 === Deploy a Neo4j cluster with SSL certificates
@@ -1155,10 +1155,10 @@ config:
 
 [IMPORTANT]
 ====
-`sub` is the only claim guaranteed to be unique and stable. 
-Other claims, such as `email` or `preferred_username`, may change over time and should *not* be used for authentication. 
-Neo4j may assign permissions to a user based on this username value in a hybrid authorization configuration. 
-Thus, changing the username claim from `sub` is not recommended. 
+`sub` is the only claim guaranteed to be unique and stable.
+Other claims, such as `email` or `preferred_username`, may change over time and should *not* be used for authentication.
+Neo4j may assign permissions to a user based on this username value in a hybrid authorization configuration.
+Thus, changing the username claim from `sub` is not recommended.
 For details, see https://learn.microsoft.com/en-us/azure/active-directory/develop/id-tokens#using-claims-to-reliably-identify-a-user-subject-and-object-id[Microsoft documentation] as well as the https://openid.net/specs/openid-connect-core-1_0.html#ClaimStability[OpenId spec].
 ====
 
@@ -1375,6 +1375,7 @@ volumes:
   data:
     mode: defaultStorageClass
   licenses:
+    disableSubPathExpr: true
     mode: volume
     volume:
       secret: