Use WPILib Artifactory mirror instead of Maven Central

[mcm001]

Description

By hitting WPIlib's Artifactory Maven Central mirror instead of Maven Central, we should reduce the number of 403 flakes we see during workflow runs. This also removes jogamp from the repository list, as jogamp dependencies were removed in #1926.

Meta

Merge checklist:

• Pull Request title is short, imperative summary of proposed changes
• The description documents the what and why
• If this PR changes behavior or adds a feature, user documentation is updated
• If this PR touches photon-serde, all messages have been regenerated and hashes have not changed unexpectedly
• If this PR touches configuration, this is backwards compatible with settings back to v2025.3.2
• If this PR touches pipeline settings or anything related to data exchange, the frontend typing is updated
• If this PR addresses a bug, a regression test for it is added

[Gold856]

For redundancy, can we have both? I'd prefer to hit Maven Central first, then fall back to Artifactory if needed.

[mcm001]

We can have both. Should we prefer to hit wpilib's infrastructure instead of Maven central's?

[Gold856]

It doesn't particularly matter I think. May as well try and hit Maven Central less.

[Gold856]

For posterity, this does leave Maven Central in as an alternate repository, but Gradle will hit WPILib's Artifactory first. Maven Central is now just a fallback.

[rzblue]

Late, but if you hit maven central first it won't get cached in WPILib's Artifactory. Hitting Artifactory first is fine and will really only fail if it's not already cached and maven central is down/denies Artifactory's request.

[samfreund]

Late, but if you hit maven central first it won't get cached in WPILib's Artifactory. Hitting Artifactory first is fine and will really only fail if it's not already cached and maven central is down/denies Artifactory's request.

My understanding is that the hits go in the order that they're listed, so if we list the WPILib artifactory first we should hit that prior to Maven Central.