ActiveMQArtemis CRDs v1.0.0 are not backward compatible with v0.20.1

[brusdev]

The redeliveryDelayMultiplier and RedeliveryCollisionAvoidanceFactor fields are *float32 in v2alpha5/v0.20.1 and they are *string in v2alpha5/v1.0.0.

[gtully]

in the absence of a webhook conversion, supporting both types is not an option. further more, the inability to parse the v2alpha5 causes all operator watches to fail, leading to a head of the queue blocking problem, and the operator cannot get notification of further cr changes. Given that there is an alternative way to configure address settings in v1beta1 via broker properties and given that we don't yet have webhook conversion, and even that would have trouble with the type variance, the best option is to ignore these fields going forward.

[gtully]

with this change, it won't be possible to create new cr's with redeliveryDelayMultiplier or redeliveryCollisionAvoidanceFactor AddressSettingsType fields in yaml:

$ kubectl apply  -f ./examples/artemis-basic-address-settings-deployment.yaml 
error: error validating "./examples/artemis-basic-address-settings-deployment.yaml": error validating data: ValidationError(ActiveMQArtemis.spec.addressSettings.addressSetting[1]): unknown field "redeliveryDelayMultiplier" in io.amq.broker.v1beta1.ActiveMQArtemis.spec.addressSettings.addressSetting; if you choose to ignore these errors, turn validation off with --validate=false

If necessary, they will have to be added to the brokerProperties Spec attribute.

Spec.BrokerProperties:
 - "addressSettings.#.redeliveryDelayMultiplier=2.1"
 - "addressSettings.#.redeliveryCollisionAvoidanceFactor=1.2"