Bring the project's GitHub Actions usage down

### Description

According to [this email notification](https://lists.apache.org/thread/775w75c3fsc3qnhsmszrrgwrrzqvffzn), we need to bring the project's GitHub Actions usage down.

* Streamline long-running builds — make individual jobs faster/shorter.
* Minimize concurrent builds — reduce how many jobs run at the same time

GitHub Actions Statistics, gluten:
https://infra-reports.apache.org/#ghactions&project=gluten&hours=168&limit=15&group=name

Possible ways:
* https://github.com/apache/gluten/issues/11997
* Trigger tests based on path filters more specifically. For example, any changes under ./dev will trigger the workflows, but some of scripts are just tools, not for building, which can be filtered out.

Start by reviewing the project's GitHub Actions workflow definitions and the linked GitHub Actions Statistics report for gluten. Identify long-running or unnecessarily concurrent jobs and broad ./dev path triggers, then narrow or streamline the workflows. Done means the relevant builds run for fewer changes and consume less Actions usage without losing required validation.

Written by the indexing model from the issue text.