feat: Added DPP visualization and EcoPass KIT

[matbmoser]

WHAT

• Moved items to industry-core-kit
• Updated kit-features to be dynamic
• Added eco-pass-kit functionality

WHY

Currently, most of the feature configuration was hardocoded and not fitting to the overall architecture from the side bar.

FURTHER NOTES

List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc.

Closes # <-- insert Issue number if one exists

[github-actions]

🧪 Test Summary

🎉 Status: SUCCESS

📊 Backend Tests

Passed	Failed	Total	Coverage
✅ 147	❌ 0	📋 147	📈 57.20%

Run Details

• Branch: 391/merge
• Commit: e71eb2b8923527548128a273b102fa0c675029d4
• Trigger: pull_request

[CDiezRodriguez]

Excellent work. I’ve tested it successfully in both my local environment and our cloud environment.

In general, we should avoid putting resource-release logic directly into __del__. Instead, define an explicit cleanup method like close() that callers can invoke deterministically (or use via a context manager), and have __del__ delegate to that method. This keeps __del__ simple while preserving existing behavior.

For this specific file (ichub-backend/managers/enablement_services/adapters/http_submodel_adapter.py), we can:

1. Extract the logic from __del__ into a new close(self) -> None method on HttpSubmodelAdapter.
2. Simplify __del__ so that it just calls self.close() inside a small try/except (keeping the existing safety against exceptions during garbage collection).
3. Keep logging behavior identical, so existing observability is unchanged.

Concretely, around lines 516–523:

• Replace the current body of __del__ with:
  • A close() method that:
    • Checks hasattr(self, "client").
    • Calls self.client.close().
    • Logs success.
    • Catches and logs any exceptions.
  • A simplified __del__ that just calls self.close() inside a try/except and logs a warning on error.

No new imports are needed; we reuse the existing logger and httpx client attribute.

In general, to fix “explicit returns mixed with implicit returns”, ensure that every control-flow path in the function ends with an explicit return statement, even when the function is intended to return None. For _execute_submodel_operation, the intent (per docstring and annotation) is that read operations return a Dict[str, Any] and write/delete operations return None. The most conservative fix, without changing any behavior, is to add a final return None at the end of the function body so that any path that currently falls off the end now explicitly returns None.

Since we must not assume or modify the unseen internal logic (lines 263–306), we will only add a single line at the end of _execute_submodel_operation, immediately before the next method definition (upload_twin_aspect_document). This ensures that: (1) existing explicit return statements (e.g., for read operations) still work unchanged; (2) any path without an explicit return now returns None, which matches the documented contract for write/delete operations; and (3) CodeQL’s complaint about mixed explicit/implicit returns is eliminated. No new imports or helper methods are required.