Bump bazel version to 6.1.1

[drewmacrae]

This is a WIP, it will probably need to be announced at some point to get people to update appropriately.

[timothytrippel]

Unless there is a critical work stream this is blocking, I would highly suggest we postpone doing this for a couple months. This could impact the infrastructure that runs our nightlies, and may require medium -- significant effort to get things working again.

CC: @moidx

[moidx]

Agreed. At this moment we don't have enough bandwidth to support updates to nightlies and physical design workflows. We can pick this up again later once we have a separate branch for earlgrey.

[drewmacrae]

For reference this blocks:

• remote execution which needs 6.0.0+ and could be useful to developing CI and other test frameworks that deliver resources to teams instead of individuals and on a per-action basis instead of per-test job (which should help to cache CI runs more flexibly)
• better FPGA allocation which needs 6.1.0+ and runs the first FPGA test as soon as it's ready which should improve CI performance and performance on everyone's workstations.
• There are also improvements to dependency management that I haven't yet looked into.

In all, the better test performance will offer a nice ROI, but it's only critical in the sense that it gives us better tools to address some of the performance issues and dependency management it looks like we're struggling with at present.