[SPARK-55115][INFRA] Use master branch's base Dockerfile for release builds

### What changes were proposed in this pull request?

Modified the release GitHub Actions workflow to always use master branch's `Dockerfile.base` when building the release Docker image, instead of using the `Dockerfile.base` from the release branch.

### Why are the changes needed?

Old branch Dockerfiles can become unmaintainable over time due to:

- Expired GPG keys (e.g., Node.js 12 repository keys)
- Outdated base images with broken package dependencies
- Package version conflicts with aging OS versions (e.g., Ubuntu 20.04)

The master branch's `Dockerfile.base` is actively maintained and uses modern base images (Ubuntu 22.04), making release builds more reliable. Only the base Dockerfile is pulled from master, while the main `Dockerfile` remains from the release branch to preserve any release-specific configurations.

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?

Tested locally for all the active branches with all the release steps (except for uploading)

### Was this patch authored or co-authored using generative AI tooling?

Yes. cursor 2.3.41

Closes #53890 from cloud-fan/use-master-dockerfile-for-release.

Authored-by: Wenchen Fan <wenchen@databricks.com>
Signed-off-by: Wenchen Fan <wenchen@databricks.com>