Update to allow for Laravel 11 and Laravel JSON:API v5 support

[Westie]

Description

Updates composer.json to allow for Laravel 11 and JSON:API v5.x support. Also includes bump to support PHPUnit 10 and/or PHPUnit 11 as required.

Motivation and context

Needed for Laravel 11 support.

How has this been tested?

PHPUnit 11.5.3 by Sebastian Bergmann and contributors.

Runtime:       PHP 8.3.9
Configuration: /Users/david.weston/www-data/openapi-spec-generator/phpunit.xml.dist

........                                                            8 / 8 (100%)

Time: 00:01.263, Memory: 46.50 MB

OK (8 tests, 15 assertions)

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

• I have read the CONTRIBUTING document.
• My pull request addresses exactly one patch/feature.
• I have created a branch for this patch/feature.
• Each individual commit in the pull request is meaningful.
• I have added tests to cover my changes.
• If my change requires a change to the documentation, I have updated it accordingly.

If you're unsure about any of these, don't hesitate to ask. We're here to help!

[Westie]

Actually, a question: should laravel-json-api/hashids be natively supported as part of this library?

I'll update this PR when I have an answer on laravel-json-api/hashids#2

[Rocksheep]

Thank you for contributing to the project. I see that laravel-json-api/hashids#2 has been merged. Kan you update the PR to use the new version?

[Westie]

@Rocksheep thanks for the ping! now that upstream has been properly versioned, there's new requirements that ultimately demand newer versions of phpunit

I've now sorted out the deprecation errors