Setting up File Based Catalogs for CSM Operator

[panigs7]

Description

This PR does the adds file based catalogs that defines the upgrade path and crds for a specific operator version:

• catalog.yaml file is a generated file from catalog-template
• catalog-template defines the upgrade path

GitHub Issues

List the GitHub issues impacted by this PR:

GitHub Issue #
dell/csm#1559

Checklist:

• I have performed a self-review of my own code to ensure there are no formatting, vetting, linting, or security issues
• I have verified that new and existing unit tests pass locally with my changes
• I have not allowed coverage numbers to degenerate
• I have maintained at least 90% code coverage
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works
• I have maintained backward compatibility
• I have executed the relevant end-to-end test scenarios

How Has This Been Tested?

• Build catalog image after FBC changes
• Used the catalog image to install operator followed by driver in OCP UI
  

NOTE: This does not require e2e tests or Unit tests as this PR is basically for catalog image creation of Operator with File based catalogs. This does not bring any functionality changes in Operator