fix: add cross-module prefixes for includes and xrefs in security-best-practices

Author: gtrivedi88

modules/secure/pages/security-best-practices.adoc

@@ -24,7 +24,7 @@ devEnvironments:
   defaultNamespace:
     autoProvision: false
 ----
-include::example$snip_che-curated-access.adoc[]
+include::administration-guide:example$snip_che-curated-access.adoc[]
 
 .Role-based access control (RBAC)
 
@@ -96,7 +96,7 @@ All resources and actions you can grant users permission to use in their {namesp
 |"get", "create", "delete", "list", "update", "patch", "watch"
 |===
 
-include::example$snip_che-user-granted-permission.adoc[]
+include::administration-guide:example$snip_che-user-granted-permission.adoc[]
 
 
 .Dev environment isolation
@@ -238,7 +238,7 @@ When configuring network policies for {prod},
 ensure that pods in the {prod-short} namespace can still communicate with pods in user namespaces,
 as this is required for proper functionality.
 
-For detailed instructions on implementing network policies with {prod}, see xref:configuring-network-policies.adoc[].
+For detailed instructions on implementing network policies with {prod}, see xref:administration-guide:configuring-network-policies.adoc[].
 
 .Disconnected environment
 
@@ -260,7 +260,7 @@ Open Source editor.
 Alternatively, cluster administrators can specify a different plugin registry in the Custom Resource, for example
 https://open-vsx.org that contains thousands of extensions.
 They can also build a custom Open VSX registry.
-include::example$snip_che-managing-extensions.adoc[]
+include::administration-guide:example$snip_che-managing-extensions.adoc[]
 
 [IMPORTANT]
 ====