Publish to github packages and/or maven central

[dennisvang]

The current github workflow publishes to a custom nexus repository at nexus.internal.fairdatapoint.org:

https://github.com/dennisvang/rdf-resource-resolver-fork/blob/4b4a34519d859a7e5159ff20958bab85305f19f2/pom.xml#L50-L52

To reduce the maintenance burden, it would probably be more convenient to publish to Github Packages and/or Maven Central.

Note that the original project (fairdevkit/rdf-resource-resolver) was published to github packages, but the switch to a custom nexus repo was made in 15dc5c2.

Publishing to Maven Central would be more convenient for the end-user, because github packages requires authentication even when installing a public package, but the publication setup is a bit more involved, as discussed in the Maven guide and Maven central docs.

Also from 6:

In addition we discourage the usage of <repositories> and <pluginRepositories> and instead publish any required components to the Central Repository. This applies for your own components as well as for 3rd party artifacts.

[dennisvang]

Note current FDP 1.17.1 (or 1.17.2?) is using rdf resolver version 0.1.2-SNAPSHOT:

<rdf-resolver.version>0.1.2-SNAPSHOT</rdf-resolver.version>

This comes from FAIRDataTeam/rdf-resource-resolver, although that has no releases on github, and the pom still refers to fairdevkit/rdf-resource-resolver:

    <groupId>com.github.fairdevkit</groupId>
    <artifactId>rdf-resource-resolver</artifactId>

I guess the fork should use its own groupId as mentioned in the Maven docs?

[dennisvang]

More about package naming:

• https://docs.oracle.com/javase/specs/jls/se21/html/jls-6.html#jls-6.1
• https://maven.apache.org/guides/mini/guide-naming-conventions.html (points to old spec)