Start guarded 1.10.2 releases from tags

[SkyBlade1978]

Summary

• react to matching 1.10.2-* tag pushes on the release branch
• require the tag to equal 1.10.2-<mod_version> and retain the four-part 110021 target contract
• require a successful Build, test, and audit check for the tagged commit
• dispatch the guarded default-branch release workflow as an ordinary CurseForge release

No credentials are handled by this starter. The default dispatcher still rebuilds, audits, checks credentials, waits for the
elease environment approval, and publishes Maven, CurseForge and GitHub in order.