Config follow-up: Conditions Add status tracking to Config resource

[andreaskaris]

Implements status conditions and component status tracking for the
Config custom resource to provide visibility into the reconciliation
state of managed components (ConfigMap, DaemonSets, CSIDriver, SCC).

• Add ConfigComponentStatuses type with status for each component
• Implement Progressing and Available conditions following Kubernetes
  conventions
• Add event recording for status changes
• Update controller with status subresource RBAC permissions
• Add test coverage for all status states
• Integrate status checks into lifecycle tests

The status system tracks individual component readiness and sets
overall conditions to indicate when the Config is progressing or
fully available.

Note: For conditions, I decided to follow advice from https://superorbital.io/blog/status-and-conditions/ and use positive-polarity conditions:

When a Condition’s "True" status represents normal operations, it is referred to as a “positive-polarity” condition, whereas Conditions where "False" represents this state are “negative-polarity”. Standardize all your Conditions to use the same polarity to represent normal operations. This will help avoid confusion when scanning the conditions list and seeing a mix of "True" and "False" status values during normal conditions.

In turn, my interpretation of this is that Progressing: True; Available: True is the way to indicate Availability (as opposed to Progressing: False, Available: True). That's also how Deployments do it. A progressing state on the other hand is Progressing: True, Available: False

  status:
    components:
      ConfigMap: Ready
      CsiDriver: Ready
      DaemonSet: Ready
      MetricsProxyDaemonSet: Ready
    conditions:
    - lastTransitionTime: "2025-10-23T12:58:22Z"
      message: Reconciliation complete
      reason: ReconcileComplete
      status: "True"
      type: Progressing
    - lastTransitionTime: "2025-10-23T12:58:42Z"
      message: Reconciliation complete
      reason: ReconcileComplete
      status: "True"
      type: Available

And the slightly counterintuitive (but that could be solved by removing PROGRESSING column from the short output):

[root@centos9-bpfman ~]# kubectl get config 
NAME            AGE   PROGRESSING   AVAILABLE
bpfman-config   7s    True          True

[mergify]

@andreaskaris, this pull request is now in conflict and requires a rebase.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0.00%. Comparing base (f00edc4) to head (8034a9b).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files

@@     Coverage Diff     @@
##   main   #474   +/-   ##
===========================
===========================

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.