Allow Customers to Pin Minor Fixpack Version in Openshift in IBM Cloud Satellite

When you upgrade Openshift in IBM Cloud Satellite, the latest fixpack is always applied and the customer has no way to 'pin' or specify the minor fixpack version fixpack version. This could be a problem for us because we generally upgrade our nonproduction environments within a 3 to 4 week span, and then production shortly there after. The upgrade sprint is usually 4 to 6 weeks. Our applications perform testing and validation against whatever the latest fixpack is at that time that gets installed in that particular environment. When we go to upgrade production, the production systems might be on a later fixpack if one is released, meanwhile the application testing and validation occurred on a previous version. We really have no way of knowing which fixpack is going to be applied as we perform our upgrades and have no control over the process. If an issue were to occur in production because it is under a higher fixpack than what was tested and validated in nonproduction, it opens a can of worms with management and having to try to explain why production is at a higher version than nonproduction that was not certified. I know fixpacks are generally bug fixes and security patches, but mistakes in releases do happen and eventually will happen where a fixpack breaks something inadvertently. It would be nice to pin versions so we can have absolute confidence that our applications won't be impacted as we migrate through the environments and up to production.