clean repo from securityContex tests

The only way that I found that the pod security context was
correctly propagated to the singleuser pod was by adding the
configuration to the hub.extraConfig, as we do with the
token-exchange

Author: garciagenrique

infrastructure/cluster/flux/jhub/jhub-configmap-profiles.yaml

@@ -39,9 +39,6 @@ spec:
         type: ClusterIP
 
     hub:
-      podSecurityContext:
-        fsGroup: 100
-        fsGroupChangePolicy: OnRootMismatch
       service:
         type: ClusterIP
       # network policy needs to be modified to allow access to the Rucio server
@@ -119,7 +116,7 @@ spec:
           # enable authentication state
           c.GenericOAuthenticator.enable_auth_state = True
 
-        01-custom-securityContex: |
+        01-custom-securityContext: |
 
           c.KubeSpawner.pod_security_context = {
               'fsGroup': 100,