[spring-to-quarkus] Split the rules into 2 categories to migrate Spring(Boot) to Quarkus

## Suggestion

Split the rules into 2 categories as currently a user can decide to migrate a Spring(Boot) application directly to a Quarkus application OR can adopt the strategy where they can still rely on some of the Spring annotations and use what we call "Quarkus Spring" or Spring compatibility layer on Quarkus.

If we agree, then we will have to create 2 family of rules:
- Spring(Boot) to Quarkus Spring
- Spring(Boot) to Quarkus
and to have the common rules packaged in a `shared` or `common` folder. An example of such common rule is about the rule scanning the pom.xml file to detect the Spring Boot parent to be replaced with the Quarkus BOM

Start by inspecting the existing rule directories and the rule that scans pom.xml for the Spring Boot parent and Quarkus BOM. Determine which rules are common, then organize the rest into Spring(Boot) to Quarkus Spring and Spring(Boot) to Quarkus families under a shared or common area. Done means the rules are consistently categorized without losing existing coverage.

Written by the indexing model from the issue text.