Allow psr/http-message v2

[boesing]

Q	A
Bug fix?	no
New feature?	yes
BC breaks?	no
Deprecations?	no
Related tickets	fixes #64
Documentation	So far, nothing changes
License	MIT

What's in this PR?

Provides support for psr/http-message v2

Why?

Executing tests with psr/http-message v2 won't work due to dependency conflicts.

Example Usage

/

Checklist

• Updated CHANGELOG.md to describe BC breaks / deprecations | new feature | bugfix

To Do

• Update CHANGELOG.md

[boesing]

When executing tests, plenty of checks will fail in the various implementations.
Not sure if this component should have an eye on the various implementations while having failing tests.
Might be a good info to know that something is not supported in those components but I'd not prevent PRs from getting merged due to failing tests tho.

Especially due to the fact that psr/http-message v2 is not installable as of now since none of the dev required components do support these yet (as they need this component to support v2 first).

[dbu]

thanks a lot. in #62 i fixed the ci to run the tests of all suites.

i am not quite sure how we should handle it, because there will be failures caused by the implementations that we do not fix, only highlight. maybe we could mark those ci builds as allowed to fail to make that more obvious.

[boesing]

maybe we could mark those ci builds as allowed to fail to make that more obvious.

Yah, could also be a comment to the PR where the runner says which tests are actually failing. Afaik, GHA has no such "allow_failures" as in travis. I've experimented a lot with it in the laminas CI pipeline and at least at that time was not able to have that properly marked in GITHUB UI as these checks are not properly marked yellow but AFAIR green.
So having an additional comment would be super helpful but not sure if there is already something like this available.

[dbu]

@boesing ok to close in favor of #68 ?

[boesing]

@dbu absolutely

[dbu]

maybe we could mark those ci builds as allowed to fail to make that more obvious.

Yah, could also be a comment to the PR where the runner says which tests are actually failing. Afaik, GHA has no such "allow_failures" as in travis. I've experimented a lot with it in the laminas CI pipeline and at least at that time was not able to have that properly marked in GITHUB UI as these checks are not properly marked yellow but AFAIR green. So having an additional comment would be super helpful but not sure if there is already something like this available.

ah indeed, was thinking of travis-ci it seems. actions/runner#2347