ci: Add benchmark and release_spark to build-test workflow

[ZacBlanco]

What problem does this PR solve?

Adds missing CI jobs which are critical to ensuring bolt's functionality is correct.

Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• ✨ New feature (non-breaking change which adds functionality)
• 🚀 Performance improvement (optimization)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)
• 🔨 Refactoring (no logic changes)
• 🔧 Build/CI or Infrastructure changes
• 📝 Documentation only

Description

1. Adds a benchmarks-build job to ensure benchmarks are always buildable. We don't need to run the benchmarks in CI because the environment is not stable enough to ensure consistent performance. It is up to users to run them. CI needs to just make sure they are not broken.
2. Adds release_spark to build matrix alongside release. The bolt backend is a critical part of the Gluten project. And when users build bolt for gluten they should be building with the release_spark target. This ensures that we build and test with the Gluten-compatible profile so that we know it always works.
3. Refactors the build-test action to have a common setup composite workflow
4. Fixes the CI image to put the python venv bin on the path first so the venv python and pip, and other installed pip-installed package binaries are available without having to source or activate the venv within the CI image

Performance Impact

N/A

Release Note

N/A

Checklist (For Author)

• I have added/updated unit tests (ctest).
• I have verified the code with local build (Release/Debug).
• I have run clang-format / linters.
• (Optional) I have run Sanitizers (ASAN/TSAN) locally for complex C++ changes.
• No need to test or manual test.

Breaking Changes

• No
• Yes (Description: ...)