[monorepo] consolidation of existing repositories into /product

[0x6861746366574]

Since 2022, we've made a shift from individual repositories to three distinct monorepos for the Symbol project.

We have adopted the following structure:

• /symbol: for everything to do with the core Symbol infrastructure, including the client (catapult), catbuffer, documentation, and SDKs.
• /product: for everything to do with products built on top of (or around) Symbol, including our wallet, website, explorer, and miscellaneous.
• /design: for everything related to the design team. This is carved off separately from /product due to the need for LFS.
• /kitchen-sink: hosts all of our legacy projects are no longer maintained but need to be preserved for reference or sentimental value.

However, we still have quite a lot of work left. It would be good to close this out for April, so we can start May fresh. Here are the tasks left specifically for the product monorepo.

---

The following repositories should be subfolders:

wallet:

• docs: for all wallet-related documentation, including archietcture and design documents.
• shared: contains our shared libraries, including: qr-library, symbol-hd-wallets, and symbol-uri-scheme and wallets-lib and symbol-wallet-address-book.
• mobile: contains mobile-wallet.
• desktop: contains desktop-wallet.

@yilmazbahadir - is this something you can work on next week with @OlegMakarenko? Also a question for @cryptoBeliever - should we put symbol-cli here, or place it in kitchen-sink?

faucet: consolidates both current faucet implementations.

• legacy: contains this repository.
• unified: contains this repostiory.

explorer: consolidates both our current explorer implementation and nodewatch.

• legacy: contains this repository.
• nodewatch: contains this repository.

@AnthonyLaw - is this something you can work on next week with @Jaguar0625?

---

Once we've moved everything over, we'll pull in the big guns (cc @Wayonb) to work on the Jenkins integration and then we will have eliminated a significant chunk of our repository fatigue. 💪🏻

[yilmazbahadir]

Yes, absolutely!

@yilmazbahadir - is this something you can work on next week with @OlegMakarenko?

[0x6861746366574]

Some more clarification:

• We'll need to make sure each PR to the product monorepo is at a minimum of 90% code coverage - ideally 95%. That includes both the desktop-wallet and mobile-wallet.
• We should update both desktop-wallet and mobile-wallet to use the new SDK. I've created two issues to track this here and here.
• We'll need to update both desktop-wallet and mobile-wallet to utilize shared.
• Our documentation for the wallets will need an overhaul. I think this is something @cryptoBeliever, myself and potentially OrisDorch (if I can rope him into it) can work on.