chore: Added more project links to the pom.xml

[dol]

Description:

According to https://maven.apache.org/pom.html#SCM the scm.url should be a publicly browsable repository.
Replaced git URI with URL to project page on Github.

Added issueManagement and ciManagement information to the scm section.

Took inspiration from https://central.sonatype.com/artifact/org.apache.maven/maven/4.0.0-rc-4 and their pom.xml.

The link on https://central.sonatype.com/artifact/io.opentelemetry.contrib/opentelemetry-cel-sampler/1.51.0-alpha ends up in a 404.

Before the change

After the change

The new pom.xml would look like this. Generated with ./gradlew clean publishToMavenLocal.
The scm.url points to the release version of the source code.

[trask]

makes sense to me 👍

The new pom.xml would look like this. Generated with ./gradlew clean publishToMavenLocal. The scm.url points to the release version of the source code.

this repos's tags don't have -alpha and start with v, e.g. https://github.com/open-telemetry/opentelemetry-java-contrib/tree/v1.51.0

[dol]

makes sense to me 👍

The new pom.xml would look like this. Generated with ./gradlew clean publishToMavenLocal. The scm.url points to the release version of the source code.

this repos's tags don't have -alpha and start with v, e.g. https://github.com/open-telemetry/opentelemetry-java-contrib/tree/v1.51.0

Good point. The new approach will reference the stableVersion from the version.gradle.kts. Emulated a new release locally by setting stableVersion = 1.52.0.

[trask]

@open-telemetry/java-approvers @open-telemetry/java-instrumentation-approvers if this looks good, I'll port to the other Java repos after merging