[Task]: build_wheels workflow takes too long for release candidates

[damccorm]

What needs to happen?

The Build wheels workflow currently can take up to 7 or 8 hours for release candidates (example - https://github.com/apache/beam/actions/runs/10408455748). This is problematic since it extends our time to build a release candidate from ~4 hours to ~8 hours, meaning you usually can't turn one around in a single day.

The slow piece is building the wheels on aarch64, which could relatively easily be decomposed into 2 jobs. Alternately, this could be done in a way such that we don't have to rebuild the whole wheel for the RC and can reuse the original wheel (not sure if this is possible).

Issue Priority

Priority: 2 (default / most normal work should be filed as P2)

Issue Components

• Component: Python SDK
• Component: Java SDK
• Component: Go SDK
• Component: Typescript SDK
• Component: IO connector
• Component: Beam YAML
• Component: Beam examples
• Component: Beam playground
• Component: Beam katas
• Component: Website
• Component: Infrastructure
• Component: Spark Runner
• Component: Flink Runner
• Component: Samza Runner
• Component: Twister2 Runner
• Component: Hazelcast Jet Runner
• Component: Google Cloud Dataflow Runner