- Add docs/meepctl-troubleshooting.md with restart procedures, decision
  tree for code vs chart changes, MEC standard-to-app mapping, and
  common failure scenarios
- Update README.md with quick-reference troubleshooting section and
  link to the full guide

- Update meep-acme-mn-cse docker-data acme path to acmecse to resolve source data not found errors during dockerize phase

Centralize MEC service mapping, format API console timestamps to YYYY-MM-DD HH:mm:ss, and harmonize filter toolbar background styling

Reflect meepctl CLI change where 'deploy dep' and 'deploy core' now
require explicit 'all' argument to deploy everything.

* js-apps/frontend: Create the SslTrustErrorDialog component and integrate it within app-constants and app-container to provide users with direct feedback and instructions when attempting to load the sandbox under an untrusted or bypassed self-signed SSL certificate context.
* app-container: Add an HTTPS protocol and IP address validation pattern in componentDidMount to automatically detect non-secure/untrusted raw IP connections and prompt the SSL trust warning dialog.
* sign-in-wait-dialog: Introduce a 'Cancel' close label button inside the initialization loading dialog, allowing users to abort the sign-in procedure.

Resolved an issue where transitioning between the SSL Certificate Help dialog and the Sign-In dialog caused the screen to freeze. Both transitions now wait 500ms to allow the Material UI component to finish its closing animation and clean up the shared DOM scroll locks before the next dialog is opened.

Also added a checksum optimization to build.sh to skip redundant frontend compilations when source files haven't changed, significantly speeding up development builds.

MEC apps (rnis, loc-serv, tm, dai, wais, vis, iot, sss) were all onboarded
with MEEP_SCOPE_OF_LOCALITY=MEC_SYSTEM. Per ETSI GS MEC 011, MEC_SYSTEM
means a service is discoverable by any app on any MEC host in the same
MEC system, so mec_service_mgmt correctly skipped its per-MEP filter for
every one of these services. The observable effect: querying
mep2/mec_service_mgmt/v1/services returned mep1's services too (and vice
versa) - the two MEPs were never actually isolated from each other's
service registries.

Switched these apps to MEEP_SCOPE_OF_LOCALITY=MEC_HOST across every
network scenario file, restoring per-MEP service isolation.

meep-federation (mec040) and meep-ams (mec021) are intentionally left at
MEC_SYSTEM: federation's whole purpose is cross-system service exchange,
and AMS's zone-to-MEP routing (MEEP_MEP_COVERAGE, parsed in
go-apps/meep-ams/sbi/ams-sbi.go) requires it to be reachable from apps on
either MEP to coordinate handover across MEP boundaries. Restricting
either of these to MEC_HOST would break their documented function.

Addresses rep/mec/etsi-mec-sandbox#17

When you selected "Select a network", the configuration-pane.js component told the app-container.js "Hey, we are terminating!"
But the app-container.js left the global Redux scenario state completely intact while it waited for the meep-virt-engine pods to finish terminating in the background.
Because the global Redux state wasn't cleared out immediately, configuration-pane.js was looking at the global state and saying, "Wait, there's still an active scenario in global state, but my dropdown is set to 'Select a network'. Let me sync myself with the global state!"
And BAM—it forcefully snapped the dropdown back to the simulated network.
Then, seconds later, the backend finally finished deleting pods, returned a status: inactive payload, and app-container.js finally cleared the global state.
Fix:
- **Immediate State Clearing:** Modified `app-container.js` to instantly nullify the global scenario state in Redux the exact millisecond a termination is triggered. This provides immediate visual feedback (clearing API tables) and removes the old data that was causing the auto-sync.
- **Polling Suppression:** Added a guard in `app-container.js` to completely ignore polled active scenario data as long as `terminationInProgressCount` is active.
- **Dropdown Sync Guard:** Added a check in `configuration-pane.js` to prevent the dropdown from attempting to auto-restore itself during an active termination.
- **Timeout Extension:** Increased the fallback `terminationInProgressCount` timeout from 5 seconds to 30 seconds to safely accommodate large scenario teardowns.

This commit addresses the constraints that were preventing dynamically added UEs from retaining their child processes.

Changes:
- frontend: Retain the 'processes' property on UEs when they are cloned and added via the configuration pane.
- frontend: Include 'processes' parsing inside the scenario-utils UE list generation.
- config: Enable build, dockerize, and deploy flags for meep-tc-engine in .meepctl-repocfg.yaml.

This commit introduces several UX/UI improvements to the sandbox homepage:
- Redesigned the hero section with a new, abstract network texture background.
- Fixed typography collisions by properly structuring the <h1> and <p> tags in the hero content.
- Wired the primary 'Sign In & Try It' call-to-action button to correctly trigger the login dialog.
- Added a missing material icon to the 'Live API Access' feature card.
- Improved overall element spacing and alignment.