WHAT

Add support to set the `suspended` property for a Kafka instance to kas-upgrade-configurations

WHY

Allow a Kafka instance to be manually suspended and resumed from suspension using the same or similar process that is used to upgrade the instances.

HOW

1. Currently the tool has a notation of component and version as the update target.  This needs to be generalised into an abstract target field and value that can handle values of type boolean in addition to string type handled today.
2. Think about the upgrade path to move from one configuration format to the new one.
3. Refactor the [configuration|https://gitlab.cee.redhat.com/mk-ci-cd/kas-upgrade-configurations/-/tree/main/configurations] tree to give us a separate configurations for version and suspensions updates with separate owners. Something like:
   configurations/production/
   configurations/production/versions/OWNERS
   configurations/production/versions/versions.yaml (today we call this strimzi.yaml)
   configurations/production/suspensions/OWNERS
   configurations/production/suspensions/suspensions.yaml
4. At present the Makefile causes a version upgrade to be performed on both stage and production.  Refactor this algorithm so that it additionally performs the suspension for both stage and production.

DONE

• Tool and configuration refactored to allow for instances to suspended / unsuspended according to matching criteria specified in the configuration yaml.
• Unit tests updated.