Bump nebula-test from 7.10.2 to 10.0.0

[dependabot-preview]

Bumps nebula-test from 7.10.2 to 10.0.0.

Release notes

Sourced from nebula-test's releases.

v10.0.0

Breaking change: Gradle 7 compatibility with Spock 2.0. This release is only compatible with Gradle 7 and forward due to the usage of Spock 2.0 with Groovy 3

v10.0.0-rc.1

Gradle 7 compatibility with Spock 2.0

v9.0.0

Remove transitive dependencies on guava and commons-io. cglib-nodebandobjenesismoved toruntime` scope.

This can be breaking change if you are defining custom classpath filters for runners. The API used to be com.google.common.base.Predicate now it is java.util.function.Predicate

v9.0.0-rc.3

Avoid adding testing frameworks into classpaths of project under test. It helps to avoid conflicts between Spock 2.x and old groovy if older Gradle version is specified in a test.

v9.0.0-rc.2

Additional handling of deprecations scenarios in Gradle 7

v9.0.0-rc.1

nebula-test migrated to Gradle 7 introducing Groovy 3. This major version will not work with projects using Gradle 6.x or less.

v8.2.0

Add ability to specify Gradle version which should be used for generating repositories with dummy dependencies.

v8.1.0

This version reverts previous feature to the state of the version 7.10.2 We discovered that there are problems in intended backward compatibility with Gradle 6.

v8.0.0

Add groovy3 feature variant to allow parallel support for Gradle 6 and Gradle 7. How to use the variant is documented here

v8.0.0-rc.1

Add groovy3 feature variant to allow parallel support for Gradle 6 and Gradle 7.

Commits

• f694901 Update nebula.plugin-plugin to 15.4.1
• 497b417 Merge pull request #138 from chali/Gradle7Compatibility
• 5a2b624 Gradle 7 compatibility
• e3fe4bc Merge pull request #137 from chali/RemoveDependencies
• 9dbf478 Remove guava and commons-io as an external dependencies, move mocking librari...
• df22b56 Revert Gradle 7 compatibility
• 924cbf6 Gradle 7.0
• e1b54ae Gradle 6.9
• 6c7f3e8 Update actions badge
• 24167c1 Consolidate GHA workflows into one
• Additional commits viewable 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 badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in the .dependabot/config.yml file in this repo:

• Update frequency
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)