Support --plugin-path on PluginOptions

[jonesbusy]

What feature do you want to see added?

Not sure if there is a 100% use case for this but I would be great to have an option --plugin-path on PluginOptions in addition of --plugins and --plugin-file to use an already checkout plugin (or a plugin not distributed to a update center). For example private and just installed via the .hpi

We need to see if we use this option to not perform any remote check (update center, health, remote branch PR) etc...

It would be also useful for manual testing

Instead of

 mvn org.openrewrite.maven:rewrite-maven-plugin:dryRun -Drewrite.recipeArtifactCoordinates=io.jenkins.plugin-modernizer:plugin-modernizer-core:999999-SNAPSHOT -Drewrite.activeRecipes=io.jenkins.tools.pluginmodernizer.core.recipes.IsUsingBom

We could have

plugin-modernizer (dry-run|run) --plugin-path . --recipe IsUsingBom

Upstream changes

No response

Are you interested in contributing this feature?

No response

[jonesbusy]

Easy to implement, but will cover few layer of plugin modernizer. It's not only adding naively the CLI option but also integration tests