Support Gradle wildcard version or placeholder variable in dependency management recipes

What problem are you trying to solve?

My organization regularly wildcards the patch version for projects rather than using an explicit version as it helps to avoid the churn of versioning artifacts explicitly, but we use OpenRewrite to change the versions of several artifacts at once across many repositories. We'd like to have the ability to specify a version of a.b.+ to better support this. We also use placeholders in several locations (i.e. a version of ${dependencyVersion}) which would also be helpful but might be out-of-scope for this issue. I can open another issue for this work if you'd like.

Describe the solution you'd like

When running the AddDependency recipe (or other dependency management recipes), I'd like to be able to specify version: 1.2.+ and have the resulting added dependency be wildcarded properly.

Have you considered any alternatives or workarounds?

A rawVersion property or similar would be just as useful and would allow for wildcarding and for placeholders.

Are you interested in contributing this feature to OpenRewrite?

I'd be interested in contributing but given how busy I am I likely won't be able to work on it anytime soon. I'll update if I find time to work on this.

Start at the AddDependency recipe and related dependency management recipes, then trace how version values are interpreted and rendered. Verify the desired behavior by checking that a version such as 1.2.+ is preserved correctly in the resulting added dependency; placeholder support may require separate scope clarification.