Use Ranch 2.1.0 in bazel build (backport #3401) (backport #3403)

[mergify]

This is an automatic backport of pull request #3403 done by Mergify.
Cherry-pick of d51fb99 has failed:

On branch mergify/bp/v3.8.x/pr-3403
Your branch is up to date with 'origin/v3.8.x'.

You are currently cherry-picking commit d51fb99710.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   deps/amqp_client/BUILD.bazel
	modified:   deps/rabbit_common/BUILD.bazel

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   BUILD.ranch
	both modified:   deps/rabbit/apps/rabbitmq_prelaunch/BUILD.bazel
	both modified:   deps/rabbitmq_aws/BUILD.bazel
	both modified:   workspace_helpers.bzl

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---

Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

• @Mergifyio refresh will re-evaluate the rules
• @Mergifyio rebase will rebase this PR on its base branch
• @Mergifyio update will merge the base branch into this PR
• @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

• look at your merge queues
• generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

[michaelklishin]

This has to be merged manually due to conflicts.