Feature-Request: Make control plane profiles persistent during OpenShift Service Mesh updates

1. Proposed title of this feature request
Feature-Request: Make control plane profiles persistent during OpenShift Service Mesh updates

2. What is the nature and description of the request?
When configuring control plane profiles according to https://docs.openshift.com/container-platform/4.7/service_mesh/v2x/ossm-profiles-users.html#ossm-control-plane-profiles_ossm-profiles-users, these changes are not persisted across Service Mesh updates and will require reconfiguration each time a new CSV is being created (meaning when Service Mesh is updated). This is a rather bad user experience as it prevents users from doing automated updates and required manual work after each update being done.

3. Why does the customer need this? (List the business requirements here)
It's general bad practice to edit CSV to add volumes/mounts to the respective Operator. Also these files are changing when updating and thus an alternative approach needs to be provided to manage the control plane profiles. Users should not be required to re-create certain configuration after Service Mesh is updated but rather be able to just use it and thus enable automated updates

4. List any affected packages or components.
OpenShift Service Mesh