Remote assistance revisit

[AustinChangLinksys]

Check the remote assistance functionality (Remote side) works on 2.0 version. And make sure the implementations fit guideline.

To build remote version and deploy to s3 server

[PeterJhongLinksys]

[Root cause]
Remote assistance mode in version 2.0 lacked proper UI-level protection for read-only mode. Users could interact with switches and save buttons that would trigger JNAP operations, which should be blocked in remote mode. Additionally, there was no clear visual indication to users that they were in a restricted mode.

[Solution]
Implemented comprehensive three-layer protection for remote read-only mode:

1. UI Layer Protection

   • Created RemoteAwareSwitch component that auto-disables in remote mode
   • Enhanced UiKitBottomBarConfig with checkRemoteReadOnly parameter to auto-disable Save buttons
   • Replaced all immediate-mode switches in quick_panel.dart and instant_privacy_view.dart

2. Visual Feedback

   • Added RemoteReadOnlyBanner with theme-appropriate styling (non-hardcoded colors)
   • Fixed banner layout to push content down instead of overlaying

3. Diagnostic Tool Support (Safe Operations)

   • Enabled read-only operations in remote mode: LED blinking, speed test, ping, and traceroute
   • Added whitelist for safe JNAP operations in RouterRepository
   • Applied remote restrictions to topology menu actions (reboot, pair, reset)

4. Localization

   • Added featureUnavailableInRemoteMode message in 26 languages

5. Testing

   • Added comprehensive test coverage for RemoteAwareSwitch and safe operations (14+ test cases)

All changes follow the existing architecture guidelines and are compatible with the 2.0 version.