Maven publication: adding Maven central repository

[DariusIMP]

• Editing the build.gradle.kts file in order to include a publication task for Maven central
• Added package signature (which is required for remote publications)
• Edited the CI workflows for both android and jvm publications.

[github-actions]

PR missing one of the required labels: {'dependencies', 'breaking-change', 'bug', 'documentation', 'internal', 'enhancement', 'new feature'}

[diogomatsubara]

Should we add the -PdryRun=true option to the gradle calls and add an additional input to run it in dry run mode?
I see the snapshot input already uses the input.live_run so maybe we can change the logic there?

[diogomatsubara]

Looks like we'll need the keyid as well when using gradle. Once the key id is available in the org secrets, I'll let you know and we can update.

[diogomatsubara]

@DariusIMP eclipse has updated the secrets. They also changed the variable names to conform to their internal policy. You can see the variables here: eclipse-zenoh/.eclipsefdn#18. Could you update this PR accordingly?

[diogomatsubara]

LGTM

[diogomatsubara]

Shouldn't this be reversed? If it's a snapshot, publish to the staging repository?

[DariusIMP]

I think it's ok as it is, based on the documentation from https://oss.sonatype.org/content/repositories/snapshots/