x-cancel-on-ha-failover is now false by default and can be configured...

...with the cancelOnHaFailover connection string value and with the fluent interface method WithCancelOnHaFailover. This should close the issues #218 and #121.

If you set on connection string, it can't be overridden by the fluent method, instead if you leave it disabled from connection string, you can manage the behavior per consumer with the fluent interface.

Possible breaking change for whom they was expecting a consumer shutdown after a cluster HA fail-over, now the consumer will be redeclared and continue to consume.