backport to 4.18.x - Use a shallow git clone on Jenkins when possible for main build

[apupier]

there are currently issues with disk space available on the Jenkins nodes.
Camel is one of the most consuming one. Each of its workspace for Camel core is taking 4.4G, it includes 1.4G for the .git folder. Using a shallow clone should reduce the 1.4G to 365M and gain few minutes
to the build too.

it is still fetching info for all branches. to be improved later on if we find how (to drop from 365M to 65M)

note that this backport adapts to the JDk used for Sonar (21 vs 17)

Co-authored-by: IBM Bob IDE 1.0.3

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.

AI-assisted contributions

• If this PR includes AI-generated code, commits have proper co-authorship attribution (e.g., Co-authored-by trailers) and the PR description identifies the AI tool used.