Make `spec.paused` and `spec.quiet` a boolean in an upcoming version of the CRD

[LCaparelli]

Feature Description

Unless there are plans to support other values and make it sort of an enum (which is also a breaking change), it probably makes more sense for spec.paused to be a bool. AFAICT from the code, we only use it as such anyway.

The current implementation leads to some awkwardness when using it, for example:

• in Helm charts, as part of a template, for which we need to add quotes around user input
• in Crossplane compositions, where we want to receive a bool from the user and then need to convert it to a string in order to match the current interface
• probably any abstraction built on top of this that offers the field as a bool to users

Suggested Solution (optional)

No response

Already existing or connected issues / PRs (optional)

No response

[yorugac]

Thanks for the issue, @LCaparelli! Such a change makes sense, AFAIS 👍

Btw, if we're going to break things here, we should also change spec.quiet type as well.