[DO NOT MERGE] Retrieve only one branch information on Jenkins

[apupier]

• it allows to save 365M - 63M = 302M per matrix build, so a total of 302 * (4 (matrix config) + 1 (JDK26)) x 5 (number of history build kept) = 7.5G
  (this is on top of previous gain of 27.5G in
  Use a shallow git clone on Jenkins when possible for main build #24201 )

Description

Target

• I checked that the commit is targeting the correct branch (Camel 4 uses the main branch)

Tracking

• If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

• I checked that each commit in the pull request has a meaningful subject line and body.

• I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[apupier]

I would liek to test on CI before merging in main branch. Awaiting a timeframe when the CI is less crowded.

note that jenkinsfile.deploy and Jenkinsfile.jbang should surely be able to benefit the same kind of improvements in a lower scale (no matrix) but given that the git checkout was done differently, i prefer to look at it separately

[apupier]

I would liek to test on CI before merging in main branch. Awaiting a timeframe when the CI is less crowded.

build started with the change: https://ci-builds.apache.org/job/Camel/job/Camel%20Core%20(Build%20and%20test)/job/main/1946/

[apupier]

not working, still 365M .git