Support updating Gradle programmatic Version Catalogs

[shanman190]

What problem are you trying to solve?

Enable updating of version catalogs defined within settings.gradle scripts.

Describe the solution you'd like

I think either of the following would be a reasonable solution:

• UpgradeDependencyVersion and UpgradePluginVersion also handle programmatic version catalog updates
• New recipes to perform these updates

Have you considered any alternatives or workarounds?

None exist right now without a user crafting a custom recipe.

Additional context

Originally asked for here.

Are you interested in contributing this feature to OpenRewrite?

Always. :)

[knutwannheden]

Without having given it much thought I would have gravitated towards extending the existing recipe. I also wonder if we should extend the GradleProject marker with some kind of flag that the dependencies are managed externally in TOML.

[shanman190]

Yeah, I gravitate toward updating the existing recipes as well rather than creating new ones.

As far as the flag for external dependencies in TOML, I would think that's more closely aligned to #4400 rather than this issue in particular since here the versions are declared directly within the settings.gradle file as defined here:
https://docs.gradle.org/current/userguide/version_catalogs.html#sec:programmatic-catalog-versions