Limit the editability of managers in a program.

[anthonymarkQA]

Describe the bug

Currently when a program is created, OpenSPP automatically generates a configuration manager, 1 for each setting, ex: cycle manager, entitlement manager etc.. these managers are linked to this particular program only.

Issues:

Problem occurs when you try to reuse managers.

ex:

1. program 1 has cycle manager 1
2. program 2 has cycle manager 2
3. replace cycle manager 2 with cycle manager 1 in program 2
4. generate cycle in program 2 => generates a cycle named cycle 1
5. generate cycle in program 1. => displays an error because cycle manager 1 already created a cycle named cycle 1 from program 2

It would be difficult to track which programs the configuration managers originated from, which would lead to problematic data in the originating programs.

To Reproduce

Expected behavior Hide access to Configuration to avoid being able to create configuration managers

Hide access to certain elements in Configuration within a program to avoid conflicts

This ticket's objective is to ensure only the configuration managers of the particular program currently selected may be edited.

Screenshots

Additional context

🔔 Note: This ticket should address common considerations without including country-specific content. Please ensure all references are generic and applicable across various contexts.