Support starting Iceberg REST catalog via CRD #678

Part of https://github.com/stackabletech/internal-issues/issues/156

Starting with Hive 4.2.0 it can start a Iceberg REST catalog (4.1.0 was broken).

In nifi-op we alread start a REST catalog in a HMS: https://github.com/stackabletech/nifi-operator/blob/4d02ceb039159bb1d71827d9ffac94d6da5424a3/tests/templates/kuttl/iceberg-rest/30_hive.yaml.j2#L31-L36.
It looks like the REST catalog is also available standalone component, we should research that. In this implementation we should try to use the standalone component and not start a thrift AND a REST catalog simultaneously to reduce complexity and potential miss-use.

It must support

• No authentication
• OAuth2 authentication
• We researched if HTTPS is possible

We need to do

• Decision: https://github.com/stackabletech/decisions/issues/105
• Operator implementation feat: Support starting Iceberg REST catalog #783
• Fix for Hive 4.2.x: fix(hive): Fall back to the managed warehouse in the Iceberg REST catalog docker-images#1722

"Unrelated" PRs

• fix(versioned): Make changedValues in tracking status optional operator-rs#1325
• fix(versioned): Allow any JSON value in tracked changed values operator-rs#1326
• feat(versioned): Add support for the removed field action operator-rs#1324