…to 4.1.1 [skip ci]

Bumps [io.github.ascopes:protobuf-maven-plugin](https://github.com/ascopes/protobuf-maven-plugin) from 4.0.3 to 4.1.1.
Release notes

*Sourced from [io.github.ascopes:protobuf-maven-plugin's releases](https://github.com/ascopes/protobuf-maven-plugin/releases).*

> v4.1.1
> ------
>
> * Reworked plugin resolution to be able to run in parallel.
> * Consistent generation of plugin ID naming is now enforced across all protoc plugin kinds.
> * JVM plugin executable generation is now abstracted, internal paths have changed slightly so users may want to run `mvn clean` on projects when updating to ensure any old files are cleaned up.
> * `plugins` specification order is now retained internally. This does not influence execution order (which is what the order param is to be used for by consumers), but does influence the naming of internally generated files. This leads to stronger buildvconsistency guarantees when updating this Maven plugin in the future.
> * Removed some incorrectly documented attributes from documentation that did not exist for certain protoc plugin variants.
>
> v4.1.0
> ------
>
> This release implements a new way of specifying `protoc` plugins. Whilst the old mechanism still works, it is now deprecated for removal in v5.0.
>
> Plugins are now specified as a discriminated list with a `kind` attribute.
>
> For example:
>
> ```
> <plugin>
>   <groupId>io.github.ascopes</groupId>
>   <artifactId>protobuf-maven-plugin</artifactId>
>   <version>4.1.0</version>
>
> <configuration>
> <plugins>
> <plugin kind="binary-maven">
> ...
> </plugin>
> </plugins>
> </configuration>
> </plugin>
> ```
>
> See <https://ascopes.github.io/protobuf-maven-plugin/using-protoc-plugins.html> for full details of usage, with examples.
>
> This paves the way for cleaning up some ugly parts of the API in v5.0, as well as supporting consistency with [GH-877](https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/877) which aims to allow eventually using WASM distributions of `protoc` as an optional alternative to platform-specific binaries.


Commits

* [`fd28a80`](ascopes/protobuf-maven-plugin@fd28a80) [maven-release-plugin] prepare release v4.1.1
* [`cf85175`](ascopes/protobuf-maven-plugin@cf85175) Set 'since' tags for v4.1.1
* [`d289f52`](ascopes/protobuf-maven-plugin@d289f52) Merge pull request [#888](https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/888) from ascopes/task/gh-877-consolidate-plugin-resolvers
* [`cd20ebe`](ascopes/protobuf-maven-plugin@cd20ebe) [GH-877](https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/877): Consolidate logic for protoc plugin resolution into one class
* [`f8135f7`](ascopes/protobuf-maven-plugin@f8135f7) Remove erroneous documentation regarding path plugins and digests
* [`190705a`](ascopes/protobuf-maven-plugin@190705a) Merge pull request [#887](https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/887) from ascopes/task/gh-877-reusable-java-app-generator
* [`b8f83d9`](ascopes/protobuf-maven-plugin@b8f83d9) [GH-877](https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/877): Fix failing ITs
* [`33ebca4`](ascopes/protobuf-maven-plugin@33ebca4) [GH-877](https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/877): Extract logic for generating executables from Java into scripts
* [`31a6b09`](ascopes/protobuf-maven-plugin@31a6b09) Merge pull request [#886](https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/886) from ascopes/task/gh-879-examples
* [`230cc76`](ascopes/protobuf-maven-plugin@230cc76) [GH-879](https://redirect.github.com/ascopes/protobuf-maven-plugin/issues/879): Improve IT examples for dependency usage
* Additional commits viewable in [compare view](ascopes/protobuf-maven-plugin@v4.0.3...v4.1.1)
  
[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility\_score?dependency-name=io.github.ascopes:protobuf-maven-plugin&package-manager=maven&previous-version=4.0.3&new-version=4.1.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
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-automerge-start)
[//]: # (dependabot-automerge-end)
---
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 show  ignore conditions` will show all of the ignore conditions of the specified dependency
- `@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)