Reconcile secrets - customPolicies

WHY

We need to make a clear distinction between secrets that should be reconciled and ones that should be created by a customer/user. 

WHAT

When OAS3 stored in secret is changed, ActiveDoc object in 3scale is not reconciled.

Note: This is a bug because our operator supports capabilities, see operator description - "Reconcilliation Tunable CRD parameters after 3scale API Management solution is installed"

HOW

Catalog all secrets and if they are created by Operator or User.

See open PR for pattern for reconciling secrets that do need to be reconciled. 

Edge Case: Some secrets such as system-seed are initially created by the operator but can be edited by customers. In this case should be operator still reconcile this secret? This is a bootstrapping secret. Bootstrapping secrets should be a one time reconcile? 

/// dev notes

see work done in apicast operator

https://github.com/3scale/apicast-operator/pull/170

DONE

All secrets have been documented as created by Operator or User.

Docs: Work with the docs team to document all secrets that should be created by the user of the Operator.