Fix swift lint errors

[nan-li]

Description

One Line Summary

Fix swiftlint errors so that our linting and CI can succeed.

Details

1. Ran swiftlint --fix commit

• This remedied auto-correctable issues like trailing whitespace, unnecessary brackets

2. Organize User module files commit

• Make folder for Executors and move executor files into this folder
• Put OSUserExecutor class into its own file, removed from the OSUserRequests mega-file
• Make folder for Requests and move request-related files to this folder
• Split up each request from OSUserRequests mega-file into its own file
• Now OSUserRequest.swift will contain just the protocol and an extension of OneSignalRequest

3. Organize OSUserExecutor functionality with a class extension commit

• This is motivated by this swiftlint error about a class having too many lines in it:

"...OSUserExecutor.swift:36:1: error: Type Body Length Violation: Type body should span 350 lines or less excluding comments and whitespace: currently spans 401 lines (type_body_length)"

• Move the parsing functionality of the OSUserExecutor into an extension of the class
• The alternative considered would be to update the .swiftlint.yml file to override the type_body_length rule to accept a longer length.

Motivation

Part of making our CI succeed as well as actually utilizing our linter.

Scope

• Linting
• re-organizing files
• no functionality change

       

Testing

Unit testing

None

Manual testing

None, ensure SDK builds and app runs after changes.

Affected code checklist

• Notifications
  • Display
  • Open
  • Push Processing
  • Confirm Deliveries
• Outcomes
• Sessions
• In-App Messaging
• REST API requests
• Public API changes

Checklist

Overview

• I have filled out all REQUIRED sections above
• PR does one thing
• Any Public API changes are explained in the PR details and conform to existing APIs

Testing

• I have included test coverage for these changes, or explained why they are not needed
• All automated tests pass, or I explained why that is not possible
• I have personally tested this on my device, or explained why that is not possible

Final pass

• Code is as readable as possible.
• I have reviewed this PR myself, ensuring it meets each checklist item

---

This change is