[EPIC] Mobile controller decoupling

[Cal-L]

What is this about?

This is an epic that tracks the controller decoupling work as outlined here here - https://www.notion.so/metamask-consensys/Architecture-decoupling-refinement-175f86d67d68806c8f2cdfd32ec83544?pvs=4 with the main goal of increasing developer velocity by also decoupling code ownership.

Tasks:

• Create foundation for modular controller init #12873
• Decouple ApprovalController from controller #12874
• Decouple PreferencesController from controller #12875
• Decouple NetworkController from controller #12876
• Decouple AssetsContractController from controller #12878
• Decouple AccountsController from controller #12879
• Decouple NFTController from controller #12877
• Decouple LoggingController from controller #12880
• Decouple KeyringController from controller #12881
• Decouple TransactionController from controller #12882
• Decouple SmartTransactionsController from controller #12883
• Decouple SignatureController from controller #12884
• Decouple TokenListController from controller #12885
• Decouple TokenController from controller #12886
• Decouple TokenBalancesController from controller #12887
• Decouple TokenRatesController from controller #12888
• Decouple CurrencyRateController from controller #12889
• Decouple PhishingController from controller #12890
• Decouple GasFeeController from controller #12891
• Decouple SelectedNetworkController from controller #12892
• Decouple PermissionController from controller #12893
• Decouple AddressBookController from controller #12894
• Decouple TokenDetectionController from controller #12895
• Decouple NFTDetectionController from controller #12896
• Decouple AccountTrackerController from controller #12897
• Decouple SnapController from controller #12898
• Decouple SubjectMetadataController from controller #12899
• Decouple NotificationServicesController from controller #12900
• Decouple NotificationServicesPushController from controller #12901
• Decouple AuthenticationController from controller #12902
• Decouple UserStorageController from controller #12903

Scenario

• TBD

Design

No response

Technical Details

• TBD

Threat Modeling Framework

No response

Acceptance Criteria

• TBD

Stakeholder review needed before the work gets merged

• Engineering (needed in most cases)
• Design
• Product
• QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
• Security
• Legal
• Marketing
• Management (please specify)
• Other (please specify)

References

No response