RFC9457 implementation

[doddi]

This PR is a backport of #576 which was an implementation of RFC9457 which adds problem information as a payload. Previously, the reasonPhrase prior to http2 could be used to provide extra information but since http2 this has been dropped.

The backport is required because maven 3.9.x is pinning maven-resolver to 1.9.x
. The previous work was released in 2.0.2.

Slack conversation: https://the-asf.slack.com/archives/C7Q9JB404/p1750487298498529?thread_ts=1750487298.498529&cid=C7Q9JB404
Fixes: #1501

Following this checklist to help us incorporate your
contribution quickly and easily:

• Your pull request should address just one issue, without pulling in other changes.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body.
  Note that commits might be squashed by a maintainer on merge.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied.
  This may not always be possible but is a best-practice.
• Run mvn verify to make sure basic checks pass.
  A more thorough check will be performed on your pull request automatically.
• You have run the integration tests successfully (mvn -Prun-its verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
• In any other case, please file an Apache Individual Contributor License Agreement.

[slawekjaranowski]

@doddi I would like to change a title of PR to something more descriptive ... like example: RFC9457 Implementation

it will be used in release notes,

[michael-o]

Squash and use the original commit summary

[cstamas]

No need for squashing, as we do it anyway (on GH UI or locally), no?

[doddi]

Easy enough to do anyway 👍

[doddi]

What would be the process for getting a maven-resolver release done for this change so that it can go into the next maven 3.9.x release?

[cstamas]

It should happen. We plan 3.9.11 soon, and resolver 1.x has some other update prs scheduled as well.

[slawekjaranowski]

Easy enough to do anyway 👍

We need also change commit message ... so quash on GitHub UI will be the easier

[slawekjaranowski]

@michael-o the commit subject and message from
92b46ba

will be ok for you?

[michael-o]

@michael-o the commit subject and message from 92b46ba

will be ok for you?

Exactly

[michael-o]

Commit summary and message aren't still right

[slawekjaranowski]

Commit summary and message aren't still right

Will be - after squash in GitHub

[michael-o]

Commit summary and message aren't still right

Will be - after squash in GitHub

How? GH knows nothing about the commit on master.

[slawekjaranowski]

@michael-o done in PR