Migrate CI to Docker

[gp201]

Overview

1. This PR fixes or fixes part of #[fill_in_number_here].
2. This PR does the following: [Explain here what your PR does and why]
3. (For bug-fixing PRs only) The original bug occurred because: [Explain what
   the cause of the bug was, and which PR introduced it]

Essential Checklist

• The PR title starts with "Fix #bugnum: " or "Fix part of #bugnum: ...", followed by a short, clear summary of the changes.
• I have followed the instructions for making a code change.
• I have assigned the correct reviewers to this PR (or will leave a comment with the phrase "@{{reviewer_username}} PTAL" if I don't have permissions to assign reviewers directly).
• The linter/Karma presubmit checks pass on my local machine, and my PR follows the coding style guide).
• "Allow edits from maintainers" is checked. (See here for instructions on how to enable it.)

Testing doc (for PRs with Beam jobs that modify production server data)

• A testing doc has been written: ... (ADD LINK) ...
• (To be confirmed by the server admin) All jobs in this PR have been verified on a live server, and the PR is safe to merge.

Proof that changes are correct

Proof of changes on desktop with slow/throttled network

Proof of changes on mobile phone

Proof of changes in Arabic language

PR Pointers

• Never force push! If you do, your PR will be closed.
• To reply to reviewers, follow these instructions: https://github.com/oppia/oppia/wiki/Make-a-pull-request#step-5-address-review-comments-until-all-reviewers-approve
• Some e2e tests are flaky, and can fail for reasons unrelated to your PR. We are working on fixing this, but in the meantime, if you need to restart the tests, please check the "If your build fails" wiki page.
• See the Code Owner's wiki page for what code owners will expect.

[seanlip]

Thanks @jayam04 -- the issue looks good, but I have some concerns about merging this with 6 known flakes that are likely to keep cropping up and blocking developers from merging things. It's going to make the dev workflow very tedious if developers have to keep rerunning the tests again and again.

I think it'd still be good to file the issues now, but after that, could you work with folks to try and fix them before we merge this PR? @jnvtnguyen has been doing some flake fixes recently, and might be a good person to ask for tips/help.

Thanks!

[gp201]

I have addressed some of the comments.
Will address the remaining by tomorrow:

1. Migrate CI to Docker #19962 (comment)
2. Migrate CI to Docker #19962 (comment)
3. Migrate CI to Docker #19962 (comment)
4. Migrate CI to Docker #19962 (comment)
5. Migrate CI to Docker #19962 (comment)
6. Migrate CI to Docker #19962 (comment)

[Lawful2002]

LGTM for codeowner files

[oppiabot]

Unassigning @Lawful2002 since they have already approved the PR.

[gp201]

Hi @U8NWXD,

Apologies for the trouble, and thanks for your patience. Since this PR is time-sensitive, could you quickly check out the other comments?

Right now, I'm focusing on resolving the comments provided in these two discussions:

1. Migrate CI to Docker #19962 (comment)
2. Migrate CI to Docker #19962 (comment)

[U8NWXD]

I've replied to or resolved my responded-to comments

[oppiabot]

Hi @gp201, I'm going to mark this PR as stale because it hasn't had any updates for 7 days. If no further activity occurs within 4 days, it will be automatically closed so that others can take up the issue.
If you are still working on this PR, please make a follow-up commit within 4 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!