fix: Remove incorrect status service

[adwk67]

Description

Fixes #798.

Status updates are currently sent to prometheus (correct) and the bundle-builder service, which exposes a status endpoint, but does not offer one to POST to. This has been removed.

The config now changes from

{
...
  "status": {
    "service": "stackable"
    "prometheus": true
  }
}

to

{
...
  "status": {
    "prometheus": true
  }
}

and log outputs showing previously

opa {"level":"info","msg":"Bundle loaded and activated successfully.","name":"stackable","plugin":"bundle","time":"2026-01-20T08:09:52Z","logger":"server"}
opa {"level":"error","msg":"status update failed, server replied with HTTP 404 Not Found.","plugin":"status","time":"2026-01-20T08:09:52Z","logger":"server"}

now show

opa {"level":"info","msg":"Bundle loaded and activated successfully.","name":"stackable","plugin":"bundle","time":"2026-01-20T11:57:24Z","logger":"server"}
opa {"level":"info","msg":"Status update sent successfully in response to plugin update.","plugin":"status","time":"2026-01-20T11:57:24Z","logger":"server"}

--- PASS: kuttl (160.24s)
    --- PASS: kuttl/harness (0.00s)
        --- PASS: kuttl/harness/resources_opa-latest-1.12.2_openshift-false (13.83s)
        --- PASS: kuttl/harness/smoke_opa-1.12.2_openshift-false_use-tls-false (14.95s)
        --- PASS: kuttl/harness/openldap-user-info_opa-latest-1.12.2_openshift-false (42.97s)
        --- PASS: kuttl/harness/cluster-operation_opa-latest-1.12.2_openshift-false (23.18s)
        --- PASS: kuttl/harness/keycloak-user-info_opa-latest-1.12.2_keycloak-23.0.1_openshift-false (88.89s)
        --- PASS: kuttl/harness/logging_opa-1.12.2_openshift-false (48.30s)
        --- PASS: kuttl/harness/aas-user-info_opa-latest-1.12.2_openshift-false (57.35s)
PASS

Jenins 🟢 https://testing.stackable.tech/job/opa-operator-it-custom/36

Definition of Done Checklist

• Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
• Please make sure all these things are done and tick the boxes

Author

• Changes are OpenShift compatible
• CRD changes approved
• CRD documentation for all fields, following the style guide.
• Helm chart can be installed and deployed operator works
• Integration tests passed (for non trivial changes)
• Changes need to be "offline" compatible
• Links to generated (nightly) docs added
• Release note snippet added

Reviewer

• Code contains useful comments
• Code contains useful logging statements
• (Integration-)Test cases added
• Documentation added or updated. Follows the style guide.
• Changelog updated
• Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

• Feature Tracker has been updated
• Proper release label has been added
• Links to generated (nightly) docs added
• Release note snippet added
• Add type/deprecation label & add to the deprecation schedule
• Add type/experimental label & add to the experimental features tracker

[lfrancke]

LGTM code-wise but maybe there was some intention here that I'm missing

[sbernauer]

Just for the record:
I only added status.service back than because the docs state it's required in https://www.openpolicyagent.org/docs/configuration#status.
Looks like the docs are wrong.

But anyway, we even added a metrics assertion to the smoke test in that PR, so as long as the test passes I don't care to be honest.

[adwk67]

LGTM code-wise but maybe there was some intention here that I'm missing

Checked with @sbernauer:

• we have a script in the smoke test and that checks that the expected metrics are available (which worked and still works).
• the docs state that the service name is required, but that does not actually seem to be the case.