EAP 8 ruleset does not catch old EAP BOM dependencies

When analyzing old EAP apps targeting EAP 8 it is important to capture EAP BOM imports inside the pom's `` section.

For instance, an EAP 6 app's pom.xml may contain the following BOM imports:

```xml




org.jboss.bom.eap
jboss-javaee-6.0-with-tools
${version.jboss.bom.eap}
pom
import


org.jboss.bom.eap
jboss-javaee-6.0-with-hibernate
${version.jboss.bom.eap}
pom
import



```

When migrating to EAP 8, its [migration guide](https://docs.redhat.com/en/documentation/red_hat_jboss_enterprise_application_platform/8.0/html-single/migration_guide/index#maven-artifact-changes-for-jakarta-ee_default) instructs updating to:

```xml

org.jboss.bom
jboss-eap-ee-with-tools
${version.bom}
pom
import

```

Locate the EAP 8 ruleset that analyzes Maven dependencyManagement entries and compare its handling with the old EAP BOM examples in this issue. Use the migration guide's org.jboss.bom dependency as the target case; done means old org.jboss.bom.eap BOM imports are detected for migration to the EAP 8 BOM.

Written by the indexing model from the issue text.