Figure how to run e2e tests

[mrjones-plip]

Describe the issue
As we start to write code, we need to start writing end to end (e2e) tests for #9735.

Describe the improvement you'd like
This is an unknown process so some prototyping needs to be done. May be dependent on #9737

Describe alternatives you've considered
no tests FTW \o/ (that's a bad joke, we need tests)

[tasawar-hussain]

Can i look into this?

[mrjones-plip]

@tasawar-hussain - yes - that'd be wonderful!

[jkuester]

Just to cross-link things here, we are leaning towards using KeyCloack for initial testing/development/prototyping of the OIDC functionality.

That does not mean KeyCloak will necessarily be preferable for e2e testing, though. Among other things, it is pretty heavy and full featured, so it would be a lot to spin up for a few automated tests. Not sure what other options might be available for a lightweight OIDC provider, but I did want to throw out Kanidm as an option. The main benefits I see in Kanidm for automated tests are that it is more lightweight (Rust vs Java 😬), has first-class support for configuring everything (users/services/clients/etc) via a CLI interface, and the project has first-class support for deploying with Docker.