Spike operator refactoring to remove product-config cruft, using the hello-world operator

As a dev, the way config settings are piped through from the CRD into the final k8s objects is confusing and error prone, and often a hindrance to quicker feature development. We would like to try and remove all of it, and spike this on the hello world operator since it is small and so it's easier to try out.

The refactoring should also consider dropping or replacing certain parts of the framework that are involved in the property handling.

Whoever implements this can decide whether to refactor the existing codebase or start from a blank slate, copying in code pieces as necessary.

This ticket is just about spiking the refactoring, we can still decide not to go through with it if the changes are too large.

Acceptance criteria

• a hello world operator implementation exists that is feature-identical to the existing one, but has simplified property handling without the product config. This will serve as a basis for discussion on whether changes should be made to our existing operator code bases.

Related tickets

This ticket would be a step towards fixing this one: https://github.com/stackabletech/issues/issues/338

Start by locating the existing hello world operator and tracing how CRD properties become final Kubernetes objects. Compare its current product-config and property-handling path with a simplified, feature-identical design, then record whether the spike provides a suitable basis for discussion.