Currently we need to create the MOSC resource in several ways (with and without defining the pull secret, using the internal registry or the external registry, adding an expiration label or not adding it...)

The way our automation is handling all those situations are too dirty and difficult to understand and maintain, we need to refactor this part of the code to use a clearer way to define the kind of MOSC that we want to create.

• Maybe create a param struct with all the options is enough?
• Maybe we need to create a builder struct?