Setup integration testing infrastructure: HTTP basic authentication

[travishathaway]

What is the idea?

We need to be able to run integration testing in our test suite for the authentication schemes we want to support.

Why is this needed?

In order to properly test these authentication schemes, it makes sense to have an integration testing system in place (or at least a strategy for how we intend to do this type of testing).

What should happen?

• Setup testing infrastructure #3 (this issue should be completed first)
• Setup integration testing to support HTTP Basic Authentication.
• Write several new integration tests to demonstrate how this will work
• Don't forget local testing! Make sure this can be done on a local setup as well (probably using a docker-compose.yml file)

Additional Context

To accomplish this, we will most likely take advantage of GitHub Action's "service containers". More information about those can be found here:

https://docs.github.com/en/actions/using-containerized-services/about-service-containers

[travishathaway]

This is one testing scenario that I believe needs to be covered in this repository:

• Auth handler plugin hook conda/conda#12911 (comment)

[travishathaway]

This is the test repodata server that is currently used by the mamba project:

• https://github.com/mamba-org/mamba/blob/main/mamba/tests/reposerver.py

It could be helpful for setting up integration testing for this project.

[travishathaway]

This could be a nice resource to use once we are ready to test anything related to OAuth2/OpenID:

• https://github.com/zmartzone/lua-resty-openidc