BB2-4303: Revert changes to fix selenium tests

[stiwarisemanticbits]

JIRA Ticket:
BB2-4303

What Does This PR Do?

This PR reverts some of changes which were done as part of PR #1423 as it was breaking selenium tests for mslsx locally

What Should Reviewers Watch For?

1. Checkout this branch
2. Export all aws keys from cloud tammer
3. Execute ./docker-compose/run_selenium_tests_local.sh

If you're reviewing this PR, please check for these things in particular:

Validation

What Security Implications Does This PR Have?

Please indicate if this PR does any of the following:

• Adds any new software dependencies
• Modifies any security controls
• Adds new transmission or storage of data
• Any other changes that could possibly affect security?

• Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
  security engineer's approval.

Any Migrations?

• Yes, there are migrations
  • The migrations should be run PRIOR to the code being deployed
  • The migrations should be run AFTER the code is deployed
  • There is a more complicated migration plan (downtime,
    etc)
• No migrations

[jadudm]

This rolls back some changes to the management command create_test_user..., which is only used in testing. The more invasive changes made previously broke the selenium tests---which wasn't known at the time, because the selenium tests were broken.

None of this is production pathway. It has been confirmed by two devs that the new stack tooling and selenium tests now run locally.

The unit tests have a problem. Need to check everything.

[jadudm]

All good. Passes tests locally and in CI/CD.