Ledger Nano S Hardware Wallet Support

**User Story**
As a `Ledger Nano S user` I want an implementation to `support BitShares accounts` so that I may `safely store my private keys, sign transactions and submit them to the network`.

**Additional Context**
- [ ] #1339 Hardware Wallet Support (General)
- [ ] [EOS Implementation](https://github.com/LedgerHQ/ledger-app-eos)
- [ ] [Fairy Wallet Implementation](https://github.com/tarassh/fairy-wallet)
- [ ] DasCoin Validator (white lable) Implementation [Cite]

## CORE TEAM TASK LIST
- [x] Evaluate / Prioritize Feature Request
- [x] Refine User Stories / Requirements
- [ ] Define Test Cases
- [ ] Design / Develop Solution
- [x] Initial Research:
- [x] Assigned: @christophersanborn @MarcialVieira
- [x] Estimated: 10 & 6 hours
- [x] Remittance: Weeks 46-47
- [ ] Phase I: Implementation of Nano app and basic developer utilities
- [ ] Device side: Nano app
- [x] Assigned: @christophersanborn
- [x] Estimated: between 40 and 80 hours for this component
- [x] Remittance: 10 hours in Weeks 48-49
- [x] Remittance: 15 hours in Weeks 50-51
- [x] Remittance: 36.5 hours in Weeks 1-5
- [ ] Remittance: ?? hours in Weeks 6
- [ ] Remittance: ?? hours in Weeks 7-8
- [ ] Host side: Nano App
- [x] Assigned: @marcialvieira
- [x] Estimated: between 40 and 60 hours for this component
- [x] Remittance: 24 hours in Weeks 1-5
- [ ] Remittance: ?? hours in Weeks 6
- [ ] Remittance: ?? hours in Weeks 7-8
- [ ] Phase II: User interface
- [ ] Primary Goal: A connector for Beet support.
- [ ] Primary Goal: A standalone GUI app for the Ledger app store providing basic wallet functionality
- [ ] Secondary: Integration into cli_wallet
- [ ] Secondary: Documentation and initial interface code for bitshares-ui team to use
- [ ] Perform QA/Testing
- [ ] Update Documentation

The issue names no files, tests, or entry points. Start by reviewing hardware-wallet issue #1339 and the linked EOS and Fairy Wallet implementations, then clarify the Nano app, host-side utility, UI, QA, and documentation boundaries. Done means the defined phases are implemented, tested, and documented.

Written by the indexing model from the issue text.