Describe the bug

This is a follow up to #44215, #44324 and #44279.

When comparing TestResources to determine which ones need to be started for a QuarkusIntegrationTest, only the Annotation name of a @WithTestResource is taken into account but not the annotation attributes.
In our case we use a custom TestResource to start Hoverfly with a configurable path to the relevant simulation files. At least until Quarkus 3.15.4 this worked perfectly well but due to some refactorings now this test resource is not restarted as only the annotation attribute is different, but the annotation is the same.
I only tried with Quarkus Versions 3.2X.X but this issue exists in all those versions

Most like it would be necessary to extend the TestResourceComparisonInfo with annotation attributes

Expected behavior

The test resource is restarted if the configuration differs

Actual behavior

The test resource is not restarted which leads to failing integration tests

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response