add qa script and readme

[SimoneDutto]

Description

While qa locally ReBAC Admin I made some change to the original rebac-admin-ui-handlers script to adapt it to jimm's deployment.
After discussing with @babakks we decided to add it to Jimm's repo for reproducibility.

Fixes JIRA/GitHub issue number

Engineering checklist

Check only items that apply

• Documentation updated
• Covered by unit tests
• Covered by integration tests

Test instructions

Notes for code reviewers

[kian99]

To understand better, does testing like this offer us anything beyond what our integration tests do?

[kian99]

This feels a bit flimsy because the code below will not stay up to date as the actual code changes.
Also, we don't mention what the change is doing?
Could we not run the tests with the default admin user in the docker compose?

[SimoneDutto]

this change is the easiest way to remove the authentication but keep the user in the context for the rebac-admin stuff to work.
Otherwise we need to create a cookie and use it in the bash script, or something like taht

[SimoneDutto]

@kian99 to answer you: it's not adding much to the whole integration tests. In fact it is not run in a action, it is just because @babakks mentioned that this script could be useful so he suggested to add to Jimm's repo

[kian99]

@kian99 to answer you: it's not adding much to the whole integration tests. In fact it is not run in a action, it is just because @babakks mentioned that this script could be useful so he suggested to add to Jimm's repo

In that case I'd question whether we should put it in the repo with the additional instructions on having to modify the source code to get it to run. It feels like "dead code" something that won't get used and potentially only cause confusion to someone that looks at it in a few years time. Maybe instead we could include in the readme a link to the test script in the other repo, etc.

[SimoneDutto]

@kian99 to answer you: it's not adding much to the whole integration tests. In fact it is not run in a action, it is just because @babakks mentioned that this script could be useful so he suggested to add to Jimm's repo

In that case I'd question whether we should put it in the repo with the additional instructions on having to modify the source code to get it to run. It feels like "dead code" something that won't get used and potentially only cause confusion to someone that looks at it in a few years time. Maybe instead we could include in the readme a link to the test script in the other repo, etc.

Since it is temporary until we have a proper QA from the Web Team we can even leave this PR open for reference and close the PR as soon as the QA have been done.

@babakks what do you think?