…#3232)This makes it possible to manually invoke the release workflow and skipthe pypi upload. This is useful if the release workflow was cancelled(or failed) after the pypi upload step.Work towards#3188(cherry picked from commit6610fd7)

Fixes#3209.Revert the change to `//:gazelle_binary` so that it once again onlygenerates python code. We then create a new, private target`//:_gazelle_binary_with_proto` that gets used by tests.Update docs accordingly.Longer term, I'd like to adjust the `test.yaml` file to include asection:```yamlconfig:  gazelle_binary: _gazelle_binary_with_proto```So that test cases that need to generate `(py_)proto_library` targetscan use the multi-lang Gazelle binary and that tests that do _not_ needto generate proto targets can use the single-lang Gazelle binary.However, there were some minor roadblocks in doing so and thus I'm doingthis quick-to-implement method instead.(cherry picked from commit2ed714f)

The#3058 PR has subtly changed the default behaviour of`experimental_index_url` code path and I think in order to make thingseasier by default for our users we should go back to that behaviour.And in addition to this we are starting to make use of the MinimalVersion Selection algorithm for the platforms. This in general allowsusers to configure the upper platform version for a particular wheel.This meant that we had to change the semantics of the API a little:1. Use MVS for each platform platform tag.2. Make it such that earlier entries are overridden by later ones, i.e.   `["musllinux_*_x86_64", "musllinux_1_2_x86_64"]` is effectively the   same as just `["musllinux_1_2_x86_64"]`.A remaining thing that will be left as a followup for#2747 will be tofigure out how to allow users to ignore certain platform tags.Fixes#3250---------Co-authored-by: Richard Levasseur <richardlev@gmail.com>Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>Cherry-picked from5fa1a87