Plugin versions should be configurable as project dependencies

[rowanseymour]

• [x] I have searched the issues of this repo and believe that this is not a duplicate.
• [x] I have searched the FAQ and general documentation and believe that my question is not already covered.

Feature Request

Plugins are super useful and we're now using https://github.com/monim67/poetry-bumpversion in our projects to keep __version__ in the code in sync with the version in pyproject.toml. This plugin is configured by simply adding

[tool.poetry_bumpversion.file."your_package/__init__.py"]

However, if someone builds the project and doesn't have bumpversion installed as a plugin, that is silently ignored and __version__ is not updated. We need a way to declare that building this project requires bumpversion>=x.y.z to keep builds reproducible and consistent.

Or maybe at least poetry could error if it sees a config section that doesn't correspond to core or a known plugin?

[matinone]

This would be a great feature to have, and there seems to be quite some interest based on this issue and this StackOverflow question.