chore: Use Ops.CollectStatus Event

[gatici]

Description

This PR uses new ops feature CollectStatus Event to manage status Charm. Event named "collect_unit_status" sets the status of charm automatically at the end of every hook.

Reference:

• https://ops.readthedocs.io/en/latest/#ops.CollectStatusEvent
• https://discourse.charmhub.io/t/how-to-set-a-charms-status/11771

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that validate the behaviour of the software
• I validated that new and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have bumped the version of the library

[benhoyt]

Looks good. However, I would have expected tests to be updated with Harness.evaluate_status()?

Note also @gruyaume's comment here are probably waiting for the relation-broken fix in ops: canonical/sdcore-amf-k8s-operator#53 (comment)

[gatici]

Looks good. However, I would have expected tests to be updated with Harness.evaluate_status()?

Note also @gruyaume's comment here are probably waiting for the relation-broken fix in ops: canonical/sdcore-amf-operator#53 (comment)

https://juju.is/docs/sdk/scenario is used instead of Harness in unit tests. Hence, the unit tests are all valid without any modification.