Windows build: Enable RBE build in Windows CI

[sunjayBhatia]

Commit Message:
Enable RBE build in Windows CI

• Bumps envoy-build-tools and bazel-toolchains
• Bumps envoy-build-ubuntu image tag
  • Running Windows CI via docker uses the same mechanism as Linux to find the image tag, the tags are the same for Windows and Linux images
• Temporarily adds a patch to fix rules_go for Windows RBE issue executing batch scripts, see Windows: Recent bump to rules_go breaks Windows + RBE #11657
• Tags/fixes some additional tests that fail in CI

Additional Description: N/A
Risk Level: Low, but we may observe differences in performance of Windows CI running remotely, we may need to adjust the worker pool accordingly
Testing: N/A
Docs Changes: N/A
Release Notes: N/A
Fixes #10619

[stale]

This pull request has been automatically marked as stale because it has not had activity in the last 7 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

[sunjayBhatia]

This PR will be turned into a reviewable PR once envoyproxy/envoy-build-tools#64 is merged

[sunjayBhatia]

This may cause format to fail for some PRs since the CI image is bumped to one with llvm 10 (and clang-format 10). If that is undesirable as part of this change, we can submit another to bump that dependency separately.

[stale]

This pull request has been automatically marked as stale because it has not had activity in the last 7 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions!

[sunjayBhatia]

just waiting on envoyproxy/envoy-build-tools#70 to help us generate an updated toolchain config

[wrowe]

Unclear whether the released 3.2.0 bazel version will be compatible; the final post-3.1.2 tag which picked up the the windows path fixes was;

        sha256 = "5d48b13686081f5d07dbba1271595d1bb2b5fa1d2f8c049ef15011bd4e6bdd19",
        strip_prefix = "bazel-toolchains-834b89b3f608a9aa4c212e7ee4a05b323b980a85",
        # 2020-05-21
        urls = ["https://github.com/bazelbuild/bazel-toolchains/archive/834b89b3f608a9aa4c212e7ee4a05b323b980a85.tar.gz"],

[sunjayBhatia]

Looks like the recent rules_go bump from #11581 is the culprit

Specifically this change: bazelbuild/rules_go#2488

[sunjayBhatia]

Blocked on bazelbuild/rules_go#2542

[sunjayBhatia]

Blocked by PR #11719

[sunjayBhatia]

Blocked on bazelbuild/rules_go#2542

No longer blocked on the rules_go PR, we have a patch in this PR for rules_go and an open issue here to track figuring out the true root cause: #11657

[sunjayBhatia]

cc @nigriMSFT @davinci26 if you weren't aware of this one

[wrowe]

We have rolled up all regression fixes into a single distinct PR. #11719 needs to be applied before this one.

[sunjayBhatia]

Assuming no more test flakes, this PR should be ready for review @lizan

[sunjayBhatia]

https://dev.azure.com/cncf/envoy/_build/results?buildId=43158&view=logs&j=2d2b3007-3c5c-5840-9bb0-2b1ea49925f3&t=168f295b-0553-5364-35f7-923225ecd8b3 represents a Windows build where all tests are compiled and the ones known to pass are run

[sunjayBhatia]

@lizan the TSAN failure seems to also be occurring on master, it should not be related to this change

[dio]

@sunjayBhatia merge master will help I think. Since #11760 is merged.

[sunjayBhatia]

@dio Sure, will do

Can we get a review on this soon so we don't slip behind the newly merged PRs that might cause Windows breakages again?