Remove "configure" access for `build-triage` teams on all (?) jobs

At the moment we grant some access to people to be able to perform build triage and re-runs if required.
Some of the build jobs, such as the openjdk25-pipeline jobs, have configure access for this group. This should not be required and should be restricted to the main `build` team.

This issue covers going through the jobs, identifying which are in that state, and changing the access accordingly.

Begin by locating the job access definitions for build-triage and the openjdk25-pipeline jobs, then inventory all jobs with configure permission for that team. Compare those permissions with the stated build-team boundary; done means build-triage can still perform triage and reruns but no longer has configure access, with the affected job definitions checked consistently.

Written by the indexing model from the issue text.