Move Top Level Settings to SwiftUI + Other improvements

[afterxleep]

Task/Issue URL: https://app.asana.com/0/1204099484721401/1206108402009442

Description

Getting rid of the old and ugly SettingsViewController and the related Static Storyboard View, alongside a few other changes as follows:

1. Remove SettingsViewController and a bunch of needed ViewControllers
2. Removed Storyboard views for the Top-level settings
3. Implement Top level settings using SwiftUI + MVVM approach pattern
4. Add pre-made reusable cell components for displaying standard cells, plus a "Custom" cell that accepts any view.
5. Legacy settings views (Remaining in the Settings. storyboard) are still rendered via a SwiftUI NavigationViewController to prevent breakage of theme and functionality
6. Moved strings to UserText and updated translations for all languages
7. Use DesignResourcesKit to render Settings

How to test

• Open Settings
• Validate that all top-level switches are working
• Validate that secondary views are presented when required, and changes are reflected in the Settings View
• Check Fonts and colors for oddities.
• Validate Hidden features are hidden (Internal features not shown to users. i.e Network protection and Sync)

[github-actions]

	Warnings
⚠️	PR has more than 500 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS against 43c877e

[miasma13]

Great work, I really appreciate your diligence in the approach.
Please take a look at the comments, nothing critical, couple of typos. Besides these I would also:

1. Check and fix indentation and empty lines (especially in the files for respective sections)
2. Perform (if you haven't) more in-depth testing for older iOS versions: iOS 16, iOS 15 and iOS 14 (especially if we will merge before dropping this version to make sure we won't introduce anything breaking in the last version for 14).

[afterxleep]

@miasma13 I’ve addressed your feedback, but I’m not sure why you’ve blocked the PR given suggestions are about a few typos and code style. Is there anything else I missed?

[afterxleep]

@miasma13 Keeping this open and up to date is taking a lot of time. I've merged these changes in the first subscription PR, which is ready for review here: #2259