[PM-20142] Split GlobalSettings in file in the same namespace

[elyosemite]

📔 Objective

Restructure the monolithic GlobalSettings.cs file into separate class-specific files, adhering to the Single Responsibility Principle (SRP) and Separation of Concerns (SoC), to achieve the following goals:

• Improve Maintainability:
  • Enable instant navigation to specific configuration classes (no more searching through 500+ lines)
  • Isolate changes to avoid unintended side effects in unrelated classes
• Optimize Development Workflow:
  • Reduce merge conflicts during parallel work on unrelated settings
  • Enable granular Git history for clearer change tracking

- GlobalSettings.cs (1 file, N classes)  
+ Core/Settings/  
+ ├── AmazonSettings.cs
+ ├── AppleIapSettings.cs
+ ├── BaseServiceUriSettings.cs
+ ├── BitPaySettings.cs
+ ├── DistributedCacheSettings.cs  
+ ├── DistributedIpRateLimitingSettings.cs  
+ ├── InstallationSettings.cs  
+ └── ... (1 file per class)  

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[S-Kakar]

Thank you for your contribution! We've added this to our internal Community PR board for review.
ID: PM-20142
Link: https://bitwarden.atlassian.net/browse/PM-20142

Details on our contribution process can be found here: https://contributing.bitwarden.com/contributing/pull-requests/community-pr-process.

[elyosemite]

@S-Kakar thank you for reply. However I don't have access to you Jira board because I'm contributor from the community.