breaking(integration_test_charm.yaml): Enable RBAC for microk8s tests

[dragomirp]

Enable RBAC during microk8s setup in line with the default behaviour of charmed-kubernetes/actions-operator

[dragomirp]

Set as breaking change as it may cause issues with test that don't set trust. Tested on https://github.com/canonical/pgbouncer-k8s-operator/actions/runs/12392459034/job/34593413343?pr=474

[dragomirp]

Should I also increase the microk8s-setup's timeout?

[carlcsaposs-canonical]

is the purpose of this change to test --trust?

rbac Enable Role Based Access Control for authorisation. Note that this is incompatible with some other add-ons.

from https://microk8s.io/docs/addons

will this cause incompatibilities with other addons that we use? e.g. metallb

---

I think we'll be refactoring how we work with microk8s addons during the move to charmcraft test/spread/concierge and would prefer to avoid changing defaults before then, unless there's a significant benefit

[dragomirp]

is the purpose of this change to test --trust?

Kind of. There are already tests for it in PG/PGB (enabling RBAC during the Pytest run, tests get stuck during model cleanup), but they fail on libjuju 3.6.0.0. Beyond that, RBAC would be expected in production environments.

rbac Enable Role Based Access Control for authorisation. Note that this is incompatible with some other add-ons.

from https://microk8s.io/docs/addons

will this cause incompatibilities with other addons that we use? e.g. metallb

I don't think so, at least I had no issues locally with RBAC and metallb. RBAC is also enabled by default by the actions-operator we used before switching to DPW.