Enable support of template availability per environment

SUMMARY

As it stands, the catalog is a common configuration resource shared for all deployment environments. As such, there is no way to enable or disable specific templates on a specific environment. This is useful for example if a specific template is still under development upon the time a new release is created.

To achieve this, a new catalog_CONF.json file is to be added, (following the same approach of configuration files for existing templates PR-023-CONF.json). This file will define:

• which templates are enabled per environment,
• as well as a its visibility date.

Upon opening the catalog to create a new proposal, this new CONF file is read and the UI is adapted accordingly.

ACCEPTANCE CRITERIAS / GOALS

• A catalog_CONF.json configuration file is added to the repository
• This configuration file determines:
  • Which template is available per deployment environment;
  • their visibity
    • A visibility start date dd/mm/yyyy hh:mm
    • A visibility end date dd/mm/yyyy hh:mm

Note: if no start date is define, it means it's directly visibile . In the same logic , if no visibility end date is define , it means it's visible forever (until update of this configuration file)

• When opening the Act creation wizard, the configuration file is read, and based on the host, determine the correct deployment environment and adapt the catalog UI accordingly.