feat: Support sending OAuth token to codejail service

[timmc-edx]

This supports having an authenticated codejail service in general, but in particular is to support the temporary use of the LMS as a codejail service for the CMS: #33538

The new settings are all optional, and if not provided, the current behavior does not change.

[rgraber]

I think this is worth a simple unit test

[timmc-edx]

Yep, still working on that.

[timmc-edx]

Oh, I thought this was a different PR. What sort of test are you thinking of -- checking the output of _get_codejail_client for different combinations of settings?

[rgraber]

Oh, I thought this was a different PR. What sort of test are you thinking of -- checking the output of _get_codejail_client for different combinations of settings?

Yes

[timmc-edx]

Ready for re-review.

Although, here's a thought -- do we want a waffle flag for rollout? Right now there's a Django setting, but a flag would allow us to do a percentage rollout. (Having both would look weird, of course.)

[rgraber]

Ready for re-review.

Although, here's a thought -- do we want a waffle flag for rollout? Right now there's a Django setting, but a flag would allow us to do a percentage rollout. (Having both would look weird, of course.)

Wouldn't it cause problems to have this as a Waffle flag while the remote codejail service is a SettingsToggle? Wouldn't that mean that anything without the waffle flag enabled would just throw errors?

[timmc-edx]

I was thinking of adding a waffle flag in is_codejail_rest_service_enabled, same place the existing toggle is checked. Unless both come back True, we wouldn't attempt a remote call at all.