Integrate New GitOps Repository Structure into Existing EDP Add-Ons Management

[SergK]

Is your feature request related to a problem? Please describe.
Users of the EDP cluster add-ons repository are currently limited to a single method of managing GitOps, which may not meet all project needs and preferences. We also have a number of code duplications

Describe the solution you'd like
We aim to introduce a new GitOps repository structure, inspired by the structure found in SergK/appset-addons, alongside the current structure present in epam/edp-cluster-add-ons. This should be done in a way that preserves the current repository's integrity, offering users the flexibility to choose between the new and old GitOps management methodologies.

The new structure promotes a more modular approach, categorizing configurations into distinct sections for different clusters (e.g., dev, prod), add-ons, charts, and bootstrap configurations, facilitating a more organized and scalable management system.

Describe alternatives you've considered
An outright replacement of the current structure was considered but deemed too disruptive. Keeping both structures allows for gradual adoption and reduces immediate impact on existing workflows.

Implementation Details:

• Conduct a comparative analysis between the current and proposed repository structures.
• Develop a detailed plan for integrating the new structure without affecting the current users negatively.
• Update the project documentation to reflect the availability of the new structure and guide on its adoption.
• Test the integrated structure extensively before its official release.

Additional context
Considerations for CI/CD pipeline adjustments, addon compatibility, and documentation updates should be taken into account during the implementation phase to ensure a smooth transition and adoption.