Configuration Library: Implement lazy loading & UI Update #95

Describe the current behavior
Currently, in the Configuration Library, we follow this flow:

1. Fetch all configs via /api/configs
2. Fetch versions via /api/configs/{configId}/versions
3. Fetch version details via /api/configs/{configId}/versions/{versionId}

This results in multiple API calls being triggered upfront or in quick succession, even when the user may not interact with all configurations.

• Unnecessary API calls are made for configs that the user may never open
• Increased load on the backend
• Slower UI performance due to redundant data fetching
• Current approach does not scale well with large datasets

Describe the enhancement you'd like

Refactor the UI flow to implement lazy loading:

• Initially, only fetch the list of configs /api/configs
• Defer fetching:
  • Versions /versions
  • Version details /versions/{versionId}
• Trigger these API calls only when the user selects or clicks on a specific config