Goal:

• Provide a means to declare CR objects for system users like root or clustercheck, that don't have any associated database in mariadb.
• Lifecycle management: define a password rotation mechanism for those CR objects, that doesn't cause service disruption.
• Allow those system object to be used as credentials for database healthcheck.  

Acceptance Criteria:

• current healthcheck scripts modified to rely on system user CRs.
• password rotation mechanism testable in chainsaw unit tests.
• new mechanism used by default in deployment of controlplane CR.

Open questions:

• Which component creates the system CR objects.
• Switching to system CR objects after a minor update.