migrate from databaseUsername to databaseAccount and fully use MariaDBAccount

[zzzeek]

…BAccountLead Jira: OSPRH-4095

1. controller calls EnsureMariaDBAccount up front to make sure MariaDBAccount is present
2. error code from EnsureMariaDBAccount is handled, Conditions are amended when error is returned
3. controller calls NewDatabaseForAccount instead of NewDatabase
4. GetAccountAndSecret is used to retrieve account /secret to populate template
5. GetDatabaseByName() , normally used for delete finalizers, replaced with GetDatabaseByNameAndAccount
6. CreateOrPatchAll() used to patch the Database, replacing CreateOrPatchDB / CreateOrPatchDBByName
7. controller calls DeleteUnusedMariaDBAccountFinalizers when launched pods are definitely running on a new MariaDBAccount, returns error code if present
8. PasswordSelectors that refer to database are removed
9. all databaseUser replaced with databaseAccount inside of all XYZ_types.go
10. all databaseUser replaced with databaseAccount inside of all kuttl/*.yaml
11. all default databaseUser names become databaseAccount, replacing underscores with dashes inside of all XYZ_types.go
12. all default databaseUser names become databaseAccount, replacing underscores with dashes inside of all kuttl/*.yaml
13. MariaDBAccountSuiteTests are used in controller ginkgo tests if it has them
14. 184 is merged and replaces from go.mod are removed

[zzzeek]

this one should be all set cc @stuggi

[stuggi]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: stuggi, zzzeek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [stuggi]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment