Improve release process to check for missing commits

[labkey-tchad]

Rationale

https://github.com/LabKey/internal-issues/issues/893
We've had a couple of releases this year (26.2.0 and 26.7.1) with incorrect commits due to hiccups in the release process. We have enough information when publishing to add some guard rails, checking that the expected release tag is being built.

Related Pull Requests

• N/A

Changes

• Update BuildUtils.getStandardVCSProperties to use Grgit instead of shelling out to git commands
• Throw a GradleException from BuildUtils.getStandardVCSProperties if a non-SNAPSHOT labkeyVersion build's commit does not have a matching git tag
• Add tagCheckExcludedProjects project property (-PtagCheckExcludedProjects=...) to exclude specific modules from this tag check

[labkey-adam]

@labkey-tchad @labkey-susanh Not related and not critical (timing-wise), but since we're in here and we've switched to GA versions of Spring AI, feel free to remove the one-off Spring AI milestone version handling that Susan detests. See CheckForVersionConflicts.SPRING_AI_ARTIFACT_PREFIX.

[labkey-tchad]

@labkey-tchad @labkey-susanh Not related and not critical (timing-wise), but since we're in here and we've switched to GA versions of Spring AI, feel free to remove the one-off Spring AI milestone version handling that Susan detests. See CheckForVersionConflicts.SPRING_AI_ARTIFACT_PREFIX.

Sure. I've removed the spring-ai workaround