🌱 log less values in hbmh Reconcile.

[guettli]

Logs of caph are hard to read for the human eye because they contain many key-value pairs.

Many of them are duplicated (like the namespace).

Additionally, logging nested key-value pairs should be avoided because they are hard to query. See VictoriaLogs: Key concepts

This PR is focused on the hbmh. Similar PRs could be created for other resources.

Key-value pairs before PR:

level: INFO
time: "2025-05-13T07:57:18.785Z"
file: host/host.go:1318
message: Some message
controller: hetznerbaremetalhost
controllerGroup: infrastructure.cluster.x-k8s.io
controllerKind: HetznerBareMetalHost
HetznerBareMetalHost:
  name: bm-4
  namespace: my-workspace
namespace: my-workspace
name: bm-4
reconcileID: 982b927b-9a27-4a9a-a889-df30d40f6300
HetznerCluster:
  name: my-cluster-7spww
  namespace: my-workspace
Cluster:
  name: my-cluster
  namespace: my-workspace
HetznerBareMetalMachine:
  name: my-cluster-md-bm-1-7kg97-swstk-v9hkq
  namespace: my-workspace

The string "my-namespace" is contained 5 times.

Additionally 1: when "Provisioning state changed" is logged, the duration is logged, too.

Additionally 2: The provisioning state is added as key-value pair.

Capi Docs about Logging define some guidelines. But finally:

Cluster API providers are developed by independent teams, and each team is free to define their own processes and conventions.

We should implement it the way it makes sense for us.

PR is WIP.

[janiskemper]

@guettli plz consider the official CAPI documentation, where they talk about logging the parent and other related objects: https://cluster-api.sigs.k8s.io/developer/core/logging#keyvalue-pairs. If you disagree with CAPI, please explicitly state why.