feature (shared) Created loading state enum

[JungleGiu]

📍 Context

Related subissue

Since we are planning to implement a loading state in the landing page (Parent Issue) a unique standard for handling loading state is needed across the whole app. An enum seemed the way to avoid any inconsistencies in the future development of the app.

✅ What's been done

• Created a LoadingStatus enum under src/app/shared/enums/loading-status.enum.ts with three values: LOADING, SUCCESS, and ERROR
• Exported the enum so it can be imported cleanly by any component or service
• Added a spec file (loading-status.enum.spec.ts) to verify the enum values and ensure no unintended changes are introduced in the future

🔍 Proof

🚩Notes

• The enum uses string values (e.g. LOADING = 'LOADING') instead of numeric ones for better readability when debugging or logging
• This PR does not introduce any usage of the enum yet — adoption will happen incrementally in follow-up PRs as components and services are refactored
• No breaking changes

[otrocadev]

Very simple and focused. Perfect. Let's keep going! 💪🏼

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud