provide puristic upgrade support for Spring Boot without including polish recipes

[martinlippert]

At the moment, when upgrading a Spring Boot 2.7 application to 3.2, there are a bunch of polish and best practices recipes being applied to the source code that are not really necessary when upgrading to a newer Spring Boot version. For example, some Java 17 upgrade recipe converts string literals into text blocks where appropriate. Some other polish was to remove unnecessary @Autowired annotations (from constructors), or non-necessary @PathVariable params.

We should offer a clean separation between pure upgrade recipes and polish/best practice recipes and run only the puristic upgrade recipes when users execute the upgrade command (from the command palette or the quick fix).

In addition to that we could offer polish and best practices actions as well, but separate.