Add sandbox debugging for Oppia Bazel binary builds in CI

[BenHenning]

Explanation

Add --sandbox_debug when building //:oppia in CI. This is meant to either reproduce the situation causing failures in PRs like #3489, or provide additional context in those PRs on what's going wrong.

Checklist

• The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
• The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
• The PR follows the style guide.
• The PR does not contain any unnecessary auto-generated code from Android Studio.
• The PR is made from a branch that's not called "develop".
• The PR is made from a branch that is up-to-date with "develop".
• The PR's branch is based on "develop" and not on any other branch.
• The PR is assigned to an appropriate reviewer in both the Assignees and the Reviewers sections.

[BenHenning]

Hmm. I was hypothesizing that this might have been caused by an Android tools upgrade from underneath us since the latest version of the platform tools breaks Bazel builds. I think this theory is right given the output:

java.lang.ClassNotFoundException: com.android.tools.r8.compatdx.CompatDx

I've seen this before. I need to verify that whichever underlying action we're using is now pulling the latest platform tools, but that might be difficult to verify.

[BenHenning]

Moving this discussion to an issue since this is a blocking issue for everyone.

Edit: #3510.

[oppiabot]

Hi @BenHenning, 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 3 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 3 days (and submit it for review, if applicable). Please also let us know if you are stuck so we can help you!