[RelEng] Migrate repo.eclipse.org links to new Nexus3 schema

[HannesWell]

Replace the last path segment in repo.eclipse.org URL using the following rules (with the project's short name):

• <short_name>-snapshots -> <short_name>-maven2-snapshots
• <short_name>-releases -> <short_name>-maven2-releases
• <short_name> -> <short_name>-maven2

Following the announcement at

• https://www.eclipse.org/lists/eclipse.org-committers/msg01548.html

This will hopefully fix the failure in deploying the parent-pom and sdk target to the eclipse maven snapshot repository.

In general the links in all submodules could be updated too, but atm. it seems like the redirects from the old schema still work.

[HannesWell]

This will hopefully fix the failure in deploying the parent-pom and sdk target to the eclipse maven snapshot repository.

The deployment on the master still fails, but e.g. the deployment to Maven still works even with the old URLs.
Maybe the platform JIPP is not authorized in contrast to the releng JIPP for the eclipse-maven2 repo?
I don't see a special authorization setup.

[HannesWell]

Maybe the platform JIPP is not authorized in contrast to the releng JIPP for the eclipse-maven2 repo?
I don't see a special authorization setup.

Asked the IT team for help:
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7286

[HannesWell]

Maybe the platform JIPP is not authorized in contrast to the releng JIPP for the eclipse-maven2 repo?
I don't see a special authorization setup.

Asked the IT team for help: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7286

That fixed it. The parent-pom and sdk-target are now deployed again as desired.

[HannesWell]

Asked the IT team for help: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/7286

That fixed it. The parent-pom and sdk-target are now deployed again as desired.

At the same time the deployment to Maven failed again now.
Reopened the help-desk issue and asked for help again.