topology : fix connection factory property evaluation

[laurentperez]

Proposed Changes

You can't set topology recovery using the CF configurator unless you do a trick like -Dtrue=true in JVM args

This PR is following quarkiverse/quarkus-rabbitmq-client#85 because of the root commit at e9b642f#diff-3ee7482ebddb8471bf938e29cb3b8d0704c94e0cf94fe6a67593149b99f38c69R190

Because getBoolean("true") evaluates for a System property called "true". oops

Types of Changes

• Bugfix (non-breaking change which fixes issue #see quarkus)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have read the CONTRIBUTING.md document
• I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
• All tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works

Following readme ./mvnw clean package -P '!setup-test-cluster' does not run the tests. So I don't know if a test suite will run.

Further Comments

I followed quarkiverse/quarkus-rabbitmq-client#85 (comment) to fix the root cause

I check breaking change above and signed Pivotal CLA because if someone made it work via this true=true property trick well it won't work anymore as the real property name is expected.

[acogoluegnes]

Thanks!