Regression in release-4.0 branch

[NicoNes]

This PR is my proposal to fix multiple regressions introduced by the initial commit (ae1f6ef) on branch "release-4-0" (see issue #1165).

My fix is made of 2 commits:

• First commit to rollback files where regression where spotted to their previous version from "master" branch.
• Second commit to apply back only relevant changes from initial commit (ae1f6ef) on the files that I rollback in the first commit.

@spericas in your initial commit, you have massively replace all Context by Entity in javadoc in many classes (I listed them below). I do not revert these changes but I wonder if all of them are really relevant. If not antoher issue and PR will have to be opened to fix it.

• jakarta.ws.rs.ext.Providers
• jakarta.ws.rs.core.UriInfo
• jakarta.ws.rs.core.SecurityContext
• jakarta.ws.rs.core.Configuration
• jakarta.ws.rs.core.HttpHeaders

-- Nicolas

[spericas]

@NicoNes Thanks for looking into this. Generally looks good but let's drop changes that only update import orders, especially static ones. I believe the original 4.0 branch was created too early (before my large PR) and went stale.

[spericas]

@NicoNes Let's create another issue for the Context/Entity replacement problem you identified. You can assign it to me.

[NicoNes]

@NicoNes Thanks for looking into this. Generally looks good but let's drop changes that only update import orders, especially static ones. I believe the original 4.0 branch was created too early (before my large PR) and went stale.

@spericas Ok I will drop those changes.
I wasn't sure about what do to with those static import order changes because according to the GIT history, @mkarg commit (38772e3) about reorganizing the imports, moved these imports from down to top. So I believed your changes to move them back down again was not intentional.

[spericas]

@NicoNes Thanks for looking into this. Generally looks good but let's drop changes that only update import orders, especially static ones. I believe the original 4.0 branch was created too early (before my large PR) and went stale.

@spericas Ok I will drop those changes. I wasn't sure about what do to with those static import order changes because according to the GIT history, @mkarg commit (38772e3) about reorganizing the imports, moved these imports from down to top. So I believed your changes to move them back down again was not intentional.

Sounds like we may need some consensus here. In any case, it probably shouldn't be part of this PR (or any PR not dealing specifically with that).

[spericas]

LGTM

[spericas]

@mkarg Could you review this one too?