Deploy to Maven Central Snapshots

[dmatej]

• It would help early testing of changes
• GlassFish and few other already do that
• Grizzly and Shoal were deployed today for the first time, I see you already have the central-release profile, so you could do something like we did:
  • https://github.com/eclipse-ee4j/glassfish-shoal/pull/194/changes - this is a bit overkill, I wanted to use the same profile as is already in the parent, you created another, so I believe you don't need to override everything from oss-release.
  • https://ci.eclipse.org/glassfish/view/Release/job/shoal-deploy-snapshot/ - just change:
    • Repository name (it is set twice!)
    • Default branch name to 4.x (you can create also jobs running this job for different branches; or run this manually with a branch name chosen from the list)
    • Perhaps the Bot name and email ...?
    • The command to clean deploy -V -B -Pcentral-release
    • Timeout as Jersey builds longer time
    • Email notifications

Note: If you would do that and same would did also Metro and Tyrus, we can run eclipse-ee4j/glassfish#25859 on Eclipse Jenkins CI, GitHub Actions, and not just locally. Snapshot dependencies are just temporary, but they unblock further integration and development with new features. Release with snapshot dependencies is forbidden (unfortunately Maven Central doesn't validate it now, but by default Maven Release plugin does).