Optimization: Add methods to build jobs directly without Intermediate calls

If jobname/jobfolder is already known by upstream systems, then it would be nice to be able to trigger builds with these as arguments to avoid the overhead of intermediate calls to the Jenkins master which can have a significant impact in large systems

Start by tracing the existing methods that trigger Jenkins builds and identify the intermediate calls to the Jenkins master. Determine where jobname and jobfolder are currently resolved, then define the direct-build entry points and verify that they avoid those calls while preserving existing behavior.

Vom Indexierungsmodell aus dem Issue-Text verfasst.