python-pytest-lsp fails to build with Python 3.14.0a5.

Warnings counts differ, e.g.

_______________________ test_client_capabilities_ignore ________________________

pytester = <Pytester PosixPath('/tmp/pytest-of-mockbuild/pytest-0/test_client_capabilities_ignore0')>

    def test_client_capabilities_ignore(pytester: pytest.Pytester):
        """Ensure that the client capabilities warnings can be ignored."""
    
        setup_test(pytester, "client-capabilities")
    
        results = pytester.runpytest(
            "-W",
            "ignore::pytest_lsp.LspSpecificationWarning",
        )
>       results.assert_outcomes(passed=1, warnings=0)
E       AssertionError: assert {'errors': 0,...pped': 0, ...} == {'errors': 0,...pped': 0, ...}
E         
E         Omitting 6 identical items, use -vv to show
E         Differing items:
E         {'warnings': 15} != {'warnings': 0}
E         Use -v to get more diff

FAILED tests/test_examples.py::test_examples[workspace-configuration] - Asser...
FAILED tests/test_examples.py::test_client_capabilities - AssertionError: ass...
FAILED tests/test_examples.py::test_client_capabilities_ignore - AssertionErr...


https://docs.python.org/3.14/whatsnew/3.14.html

For the build logs, see:
https://copr-be.cloud.fedoraproject.org/results/@python/python3.14/fedora-rawhide-x86_64/08671106-python-pytest-lsp/

For all our attempts to build python-pytest-lsp with Python 3.14, see:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/package/python-pytest-lsp/

Testing and mass rebuild of packages is happening in copr.
You can follow these instructions to test locally in mock if your package builds with Python 3.14:
https://copr.fedorainfracloud.org/coprs/g/python/python3.14/

Let us know here if you have any questions.

Python 3.14 is planned to be included in Fedora 43.
To make that update smoother, we're building Fedora packages with all pre-releases of Python 3.14.
A build failure prevents us from testing all dependent packages (transitive [Build]Requires),
so if this package is required a lot, it's important for us to get it fixed soon.

We'd appreciate help from the people who know this package best,
but if you don't want to work on this now, let us know so we can try to work around it on our side.