Move away from using jenkins as a CDN (dependency jobs)

We have some jobs such as https://ci.adoptium.net/job/build.getDependency/ which are being used to store third party artifacts (for availability purposes). It is not ideal for us to be using jenkins as a software distribution mechanism for anyone using our scripts.

We have already started to take some actions to reduce this but we should catalogue where we are currently doing things like this in the main build and distribution process and look for ways to reduce it.

Ref: https://github.com/adoptium/temurin-build/pull/3985 and the [associated infrastructure PR](https://github.com/adoptium/infrastructure/issues/3806) to have CycloneDX installed on the build machines. Also see the [associated slack discussion](https://adoptium.slack.com/archives/C09NW3L2J/p1730730964548829?thread_ts=1730716533.632739&cid=C09NW3L2J).

Start with the build.getDependency Jenkins job and the referenced temurin-build pull request 3985, then catalogue other Jenkins-hosted third-party artifacts in the main build and distribution process. Use infrastructure issue 3806 and the associated discussion for context; done means the current uses and reduction paths are documented.

Written by the indexing model from the issue text.