Description of problem:

RHODS basic users cannot spawn jupyter notebook from the Spawner page due to lack of sufficient permissions.

RHODS Admins are able to spawn.

The logs (rhods-dashboard-5b5999f447-66rv6-rhods-dashboard.log) in dashboard pod report:

{"level":50,"time":1669921101154,"pid":108,"hostname":"rhods-dashboard-5b5999f447-66rv6","msg":"A
 Non-Admin User (ldap-user19) made a request against an endpoint that 
requires an admin."}

{"level":50,"time":1669921101385,"pid":108,"hostname":"rhods-dashboard-5b5999f447-66rv6","msg":"Failed
 to delete notebook, notebooks.kubeflow.org \"jupyter-nb-ldap-2duser19\"
 not found}"}

Prerequisites (if any, like setup, operators/versions):

Have 2 user groups: rhods-admins, rhods-users

Steps to Reproduce

1. Log in RHODS Dashboard > Enabled as basic user A (from rhods-users group)
2. Launch Jupyter and try to spawn a notebook
3. check the outcome
4. Log in RHODS as RHODS Admin
5. repeat 2-3
6. As RHODS Admin go to Dashboard > Settings > User management 
7. add "rhods-users" among the RHODS administrators
8. repeat 2-3 using user A once again (now the user will be able to spawn)

Actual results:

users without RHODS Admin permissions cannot spawn jupyter notebook from Spawner

Expected results:

users without RHODS Admin permissions can spawn jupyter notebook from Spawner

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

RHODS v1.20.0-7

Workaround:

Additional info:

The issue does not affect workbenches in Data Science Projects