feat: new release process

[amannocci]

What is the change being made?

• Implement a new release process compliant with security rules.

Why is the change being made?

• The old release process isn't compliant with security rules and is broken.
• The new release process is a two phased approach allowing commit review at any point.

[v1v]

pre-relaese and release workflow have several things in common, so a composite action can help with removing the duplicated steps.

I miss a version validation in both workflows. So if by accident someone set an existing release as an input version, then it should fail with an error earlier.

[v1v]

A few comments. I'd like to see some validation if the version parameter points to an existing GitHub tag and fail if that's the case.

Do you think the existing documentation in https://github.com/elastic/ecs-logging-java/blob/main/CONTRIBUTING.md#releasing could be changed to reflect this set of changes?

[SylvainJuge]

Here we should probably do an extra verification step to ensure that the maven project version is the one we expect from the parameters.

[amannocci]

Ref: 16f61a6