Adds options to prefill swagger ui security schemes

[Charlesthebird]

This PR allows users to enter the parameters for each of these swagger ui instance methods using environment variables, with an option for including the currently logged in user token. The README.md is also updated with these new options.

I was able to verify that the Swagger UI instance has the information by checking the "Available Authorizations" modal after pre-filling the Swagger UI options with the following environment variables. However, I didn't have any real services set up with auth, so I didn't test the actual e2e authenticated requests that the Swagger UI should make.

VITE_SWAGGER_PREFILL_API_KEY='["api_key","{{USER_TOKEN}}"]'
VITE_SWAGGER_PREFILL_BASIC='["basic","test-username","test-pass"]'
VITE_SWAGGER_PREFILL_OAUTH='{"clientId": "your-client-id","clientSecret": "your-client-secret-if-required","realm": "your-realms","appName": "your-app-name","scopeSeparator": " ","scopes": "openid profile","additionalQueryStringParams": {"test": "hello"},"useBasicAuthenticationWithAccessCodeGrant": true,"usePkceWithAuthorizationCodeGrant": true}'

BOT NOTES:
resolves https://github.com/solo-io/solo-projects/issues/6859

[solo-changelog-bot]

Issues linked to changelog:
https://github.com/solo-io/solo-projects/issues/6859

[Worfle]

I know the full e2e wasn't tested, but nothing in the Swagger seems odd or worrisome at all.

Looks solid to me