Don't block snapshot publishing on testLatestDeps

[trask]

main is not in a great spot right now because there hasn't been a successful CI build since I bumped the version to 1.9.0-SNAPSHOT in #4675, which means there hasn't been a snapshot published for 1.9.0-SNAPSHOT, which means the example extension and distro won't build outside of CI (in CI we build the snapshots locally and use --init-script ../../.github/scripts/local.init.gradle.kts).

The reason there hasn't been a successful CI is because of a few testLatestDeps problems #4676, #4679, #4682.

But really it seems better for testLatestDeps to not block snapshot publishing (it already doesn't block releases).

[iNikem]

It seems more and more that we don't actually care that much about latest deps. Or at least we don't want to be responsible for fixing them ASAP, more like "whenever we have time for that".

[trask]

It seems more and more that we don't actually care that much about latest deps. Or at least we don't want to be responsible for fixing them ASAP, more like "whenever we have time for that".

This is a good topic, I opened #4688 to discuss further.

[trask]

Going ahead and merging since we still need a 1.9.0-SNAPSHOT.

We still open an issue on testLatestDeps failure. This PR just publishes SNAPSHOT anyways so that we don't block other activity (e.g. testing a SNAPSHOT, or in the current case publishing the first SNAPSHOT release for a particular version so that examples build locally).