Fixed #391 - added support for header authorization

[eroznik]

Added support for the Maven 3.x repository system, since I didn't want to break the current implementation(backward compatibility for current plugin users) I added a new configuration property to control which version resolution option should be used(useRepositorySystem, default=false).

The changes were tested locally using Maven 3.6.0 on Ubuntu while accessing:

• Maven Central
• self hosted Sonatype Nexus
• self hosted Gitlab (this case is the reason for the pull request/issue)

The observed behavior before the change:

• an artifact package + metadata was deleted from the local repository
• executed versions:update-properties, remote requests to the self hosted Gitlab instance failed(404, Gitlab response for unauthorized requests)
• the parent version wasn't changed

The observed behavior after the change, with useRepositorySystem=true:

• an artifact package + metadata was deleted from the local repository
• executed versions:update-properties, remote requests to the self hosted Gitlab went through, artifact metadata fetched successfully
• the parent version was updated

[eroznik]

@khmarbaise issue summary was updated to added support for header authorization which describes exactly what i wanted to accomplish with this pull request. Beside the conflicts that are current present, is there anything else required from my side to proceed with the pull request?

[github-actions]

This PR is stale because it has been open 365 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[eroznik]

Could a maintainer please look at this? Should the conflicts get resolved so the PR gets approved? Is there something that needs to be changed? Or do we close it and forget about it?

[atokle]

We need this fix.
@olamy I see that you have recent activity here. Can you help @eroznik with what is needed to get this fix merged?

[slawekjaranowski]

Looks like fixed in: #825

@eroznik thanks for your effort