chore: align package design with software component concept for cloud compliance

[MagPasulke]

Background

The current project uses package $ZASIS under software component LOCAL. This works for on-premise but causes issues with cloud-native features like DDCDS_CUSTOMER_DOMAIN_VALUE_T which rely on ABAP_LANGU_SWCMP entries.

Problem

• LOCAL software component has no language entries in ABAP_LANGU_SWCMP
• CDS views using DDCDS_CUSTOMER_DOMAIN_VALUE_T return empty results for domains in LOCAL
• Cloud-ready packages should belong to a properly registered software component

Tasks

• Evaluate creating a custom software component (e.g. ZASIS) via report RSMAINTAIN_SWCOMPONENTS
• Restructure packages to belong to the new software component
• Ensure language entries are properly maintained
• Verify DDCDS_CUSTOMER_DOMAIN_VALUE_T works after restructuring

Context

Discovered during PR #95 (custom logic catalog feature) when the text provider view ZASIS_I_ENHCATSTATTEXT returned empty results. Worked around with virtual element pattern for now.