feat: integrate option tool with extension toolkit

[chrismclarke]

Description

Main Changes

• Add support for accessing the option tool directly from within the extension app
• Add picsa header to main component

Additional Changes

• Routing added for future support of additional pages
• Components refactored into standalone module
• Material module moved into components folder
• Icon registration moved to the corresponding material module

Review Notes

The main things to test:

• Running the options tool standalone still works as expected (e.g. yarn nx serve picsa-tools-option-tool or using nx extension on vscode)
• Running the main app via yarn start works to display the option tool content at /option

Discussion

@khalifan-kfan The process of integrating one app in another is a little bit complicated, so I don't expect you to follow all the changes in this PR. But a few things to be aware of:

• If running the extension app you will still need to manually navigate to /option, in the future we will link from the home page
• The code to add custom icons has been moved into the local tool .\components\material.module.ts file
• When you add further components in the future you will want to import them into the local .\components\components.module.ts, instead of the main app.module (better support for lazy-loading)

Tracked in #106

Preview

Live preview available at https://picsa-extension-toolkit--pr120-feat-options-tool-in-iberpk1j.web.app/option

Screenshots / Videos

Option tool now appears on /option when running the extension app via yarn start The tool also inherits theming from the main app, such as country colour

[github-actions[bot]]

Visit the preview URL for this PR (updated for commit 66da35d):

https://picsa-extension-toolkit--pr120-feat-options-tool-in-iberpk1j.web.app

_{(expires Wed, 19 Apr 2023 20:03:25 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 2435c4a5f2b9750fe5c819a7a14bcf9433816983}