Draft codejail service approach doc

[robrap]

Assorted documentation tasks, including drafting an approach doc.

Acceptance Criteria:

• Draft approach doc. Note Python upgrade of Codejail.
  • See https://2u-internal.atlassian.net/wiki/spaces/AT/pages/1693483025/Codejail+Containerization+Approach+Doc
• [discovery] Catalog existing 2U codejail docs and ticket follow-up.
  • Created Confluence wiki updates for codejail service #916
• Document or ticket rollout plan for Stage/Edge/Prod.
  • Plan and execute migration to codejail service in Stage #912

Additional notes/questions:

• Draft requirements:
  • Codejail must be deployed as its own service.
  • The new service must provide the same functional results, including security.
  • The new service must provide similar or improved observability, performance, reliability, and all other technical requirements.
  • Any enhancements should be articulated.
• Document SRE dependencies; and SRE support planning to avoid blocking.
• See codejail working doc: https://docs.google.com/document/d/1BbWAIgSQ22uZ0Q7QLHFvUmD6v_5ipmkymgF3ixclIu8/edit?tab=t.0
• Who are stakeholders? Who needs to review?

[robrap]

Tim went through the doc. I'm calling this closed.