[Release][CI] Improve versions used on jobs executed on maintenance branch

### Describe the enhancement requested

As part of the creation of a release when the code freeze is implemented we usually execute jobs on the maintenance branch before creating a RC in order to validate the status of the possible RC.
When creating patch releases, for example 12.0.1, we create the maintenance branch and some jobs fail to be executed, not because the job has a problem but because of the version used.
For example:
* Some packaging jobs like wheels would work if we use either `--arrow-version 12.0.1-rc0` or `--arrow-version 12.0.1`
* Some packaging jobs like linux packages would work if we use `--arrow-version 12.0.1.dev001`
* Some R jobs will take into account the version in `r/pkgdown/assets/versions.json` and will download the previous version if not modified.

Those will run successfully if we create the Release Candidate but creating a RC takes time and we have to sign/upload sources, etcetera.

It would be good if we could trigger those jobs on the maintenance branch.

### Component(s)

Continuous Integration, Release

Start by reviewing the packaging and R jobs run on the maintenance branch, including the version source in r/pkgdown/assets/versions.json. Compare the versions required by wheels, Linux packages, and R jobs, then verify that the relevant jobs can run successfully before a release candidate is created.

Written by the indexing model from the issue text.