Create MobilityData maven packages

[davidgamez]

Description

The goal is to standardize Maven releases and clean up the existing configuration.

Scope

• Update and simplify GitHub Actions workflows related to builds and releases.
• Review, clean up, and remove unused or redundant Maven plugins.
• Ensure Maven releases are created consistently and predictably.

Release Workflow

• Snapshot releases
  • A Maven snapshot release is automatically published on every push to the master branch.
• Stable releases
  • A Maven release (non-snapshot) is published when the release workflow is explicitly triggered.

[jcpitre]

Currently we only have the entur jars in maven central.
In #186 we updated the naming of files and packages to org.mobilitydata.
But this has not been deployed yet, so it's not in maven central

FYI here are some of the current entur jars in maven central. Some might be modified or removed:

• gbfs-validator-java-api
  • A stand-alone "fat" jar that includes spring boot all dependencies jars
  • It can be run to start the api.
  • That's the jar we want gbfs-validator-java-infra to fetch
• gbfs-validator-java-cli
  • "thin" jar that includes only classes related to the CLI.
  • We might want to reconsider uploading it to maven central and instead put the "fat" jar as a release artifact.
    • mvn packages already produces such a jar that includes all dependencies necessary to run the CLI.
• gbfs-validator-java
  • A "fat" jar that contains all the depencies jars repackaged in their base .class files.
  • I am guessing it's the jar to use if someone wants to do a validation from their own java program.

[jcpitre]

@testower As part of this issue I am going to replace entur from the package names in the java files, e.g. org.entur.gbfs.validation.GbfsValidator will become org.mobilitydata.gbfs.validation.
Any objection?

[testower]

No objection