[Feat] Allow to set OCP --version to only Major.minor version

Currently, creating an SNC using MAPT cluster requires specifying the full major.minor.patch version (e.g., 4.19.5). This forces the user to manually look up the latest available patch for a given minor release. This process is inefficient and can lead to users deploying older, non-latest patch versions by mistake.

Proposed Solution:
Enhance the --version flag to accept a major.minor version string (e.g., 4.19). When a user provides this, the tool should automatically identify and use the latest available patch version within that minor release stream.

This would function as a "latest patch" alias for a specific minor version.

Benefits:

• Improves User Experience: Simplifies the command and removes the need for manual lookups.
• Reduces Errors: Prevents the accidental use of outdated patch releases.
• Increases Efficiency: Speeds up the process of creating up-to-date environments and avoiding manual updates to always set latest available image

No files or tests are named in the issue. Start at the --version argument handling and trace how available OCP patch versions are selected for MAPT cluster creation. Done means a major.minor value such as 4.19 resolves to the latest available patch in that minor release, while full major.minor.patch input continues to work.