Epic Goal

Currently, ThinPoolConfig.OverprovisionRatio can only be configure at LVMCluster creation time and not edited later.

The goal of this epic is to allow configuring this setting so that users can pick a value that fits best to their use case.

Why is this important?

Some users want to disable overprovision ratio or adjust it's value periodically according to their needs

Scenarios

1. The user want to disable overprovision on thin pools on day 2
2. The user would like to adjust overprovision ratio according to it's needs

Acceptance Criteria

• Allow changing to a smaller value down to 1, effectively disabling over-provisioning
• Allow changing to a bigger value (esp from 1 to e.g. 10), effectively enabling over-provisioning
• No impact on existing clusters / installations.

Previous Work (Optional):

1. A spike to refine the epic: https://issues.redhat.com/browse/OCPEDGE-1084 

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>