[LIVE-10526][LLM] Fix navigation to firmware update

[ofreyssinet-ledger]

✅ Checklist

• npx changeset was attached.
• Covered by automatic tests. Too much refactoring needed (mocking etc.) to test the full navigation flows here, for now, unfortunately.
• Impact of the changes:
  • New firmware update flow (Stax):
    • Navigation to firmware update from: (and navigation back, when closing the screen or when finishing the update)
      • Wallet screen
      • My Ledger screen
      • Stax onboarding (early security checks)
        • Non onboarded LL
        • Onboarded LL
  • Old firmware update flow (Nano S, SP and X, via USB, Android)
    • Navigation to firmware update (and back) from:
      • Wallet screen
      • My Ledger screen

📝 Description

Issue: There is an issue sometimes when navigating to the (new) firmware update flow: the Tab Bar at the bottom of the screen doesn't hide properly.
Reason: This is because we have done something wrong with the navigation setup for the FirmwareUpdate and it was inside the MainNavigator which is the navigator that has the Tab Bar. We have done a hacky workaround to hide the TabBar when the Firmware update screen is displayed but it's not the proper way to do it.
Solution: Moving the FirmwareUpdate screen out of the MainNavigator, directly in BaseNavigator, and also in SyncOnboardingNavigator (for the "early security checks" flow of the onboarding).

On top of that, I've done some refactoring of the navigator/screen names and directory names for the My Ledger section because it was very confusing. (Manager is now called My Ledger in the UI, and the naming for the two screens, Manager and ManagerMain was just confusing and impossible to understand on the first try).
The 2 screens of MyLedgerNavigator are now called: MyLedgerChooseDevice and MyLedgerDevice, I hope it is now self explanatory.

❓ Context

• JIRA or GitHub link: LIVE-10526

---

🧐 Checklist for the PR Reviewers

• The code aligns with the requirements described in the linked JIRA or GitHub issue.
• The PR description clearly documents the changes made and explains any technical trade-offs or design decisions.
• There are no undocumented trade-offs, technical debt, or maintainability issues.
• The PR has been tested thoroughly, and any potential edge cases have been considered and handled.
• Any new dependencies have been justified and documented.
• Performance considerations have been taken into account. (changes have been profiled or benchmarked if necessary)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

5 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
ledger-live-docs	⬜️ Ignored (Inspect)	Visit Preview		Apr 4, 2024 2:51pm
ledger-live-github-bot	⬜️ Ignored (Inspect)	Visit Preview		Apr 4, 2024 2:51pm
native-ui-storybook	⬜️ Ignored (Inspect)	Visit Preview		Apr 4, 2024 2:51pm
react-ui-storybook	⬜️ Ignored (Inspect)	Visit Preview		Apr 4, 2024 2:51pm
web-tools	⬜️ Ignored (Inspect)	Visit Preview		Apr 4, 2024 2:51pm

[mcayuelas-ledger]

LGTM for Hub part