Pin dependencies

Hi there,

As #1107 was introduced by a new minor update to a maven task run in the release process I was wondering what you would think of (optionally?) pinning all used dependencies? Package managers don't seem to rapidly change their publishing workflows so I would assume what works now should also work in the future, so there is not necessarily a need to stay on top of all dependency updates. I'd love to have an option to limit the impact of dependency updates so that my main workflows can remain stable.

I'm more than happy to do a PR if you feel like this is a valuable addition to the project.

Start by tracing the release process and the Maven task referenced through #1107; the issue names no files or tests. Determine which dependencies are currently resolved dynamically, and define done as an optional pinning mode that keeps main workflows stable without forcing dependency updates.

Written by the indexing model from the issue text.