Update symfony/phpunit-bridge requirement from ^4.1 || ^5.0 || ^5.2 to ^6.0.0

[dependabot[bot]]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Updates the requirements on symfony/phpunit-bridge to permit the latest version.

Release notes

Sourced from symfony/phpunit-bridge's releases.

v6.0.0

Changelog (https://github.com/symfony/phpunit-bridge/compare/v6.0.0-RC1...v6.0.0)

• no significant changes

Changelog

Sourced from symfony/phpunit-bridge's changelog.

CHANGELOG

5.3

• bumped the minimum PHP version to 7.1.3
• bumped the minimum PHPUnit version to 7.5
• deprecated the SetUpTearDownTrait trait, use original methods with "void" return typehint.
• added logFile option to write deprecations to a file instead of echoing them

5.1.0

• ignore verbosity settings when the build fails because of deprecations
• added per-group verbosity
• added ExpectDeprecationTrait to be able to define an expected deprecation from inside a test
• deprecated the @expectedDeprecation annotation, use the ExpectDeprecationTrait::expectDeprecation() method instead

5.0.0

• removed weak_vendor mode, use max[self]=0 instead

4.4.0

• made the bridge act as a polyfill for newest PHPUnit features
• added SetUpTearDownTrait to allow working around the void return-type added by PHPUnit 8
• added namespace aliases for PHPUnit < 6

4.3.0

• added ClassExistsMock
• bumped PHP version from 5.3.3 to 5.5.9
• split simple-phpunit bin into php file with code and a shell script

4.1.0

• Search for SYMFONY_PHPUNIT_VERSION, SYMFONY_PHPUNIT_REMOVE, SYMFONY_PHPUNIT_DIR env var in phpunit.xml then in phpunit.xml.dist

4.0.0

• support for the testLegacy prefix in method names to mark a test as legacy has been dropped, use the @group legacy notation instead
• support for the Legacy prefix in class names to mark tests as legacy has

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.