[#581] Set the version of tuist to latest

- Update other gems
- Finish SwiftUI/SPM migration and cleanup
- drop leftover UIKit helpers and simplify Sourcery template
- move Tuist packages into Project.swift and switch targets to `.package`
- remove workspace deletion; open project directly; add documentation for dependencies
- clean README/wiki/CI configs to reflect SwiftUI + SPM-only setup
- delete CocoaPods gems/steps, adjust Danger/Fastlane scripts, update Fastlane constants
- remove Podfiles, UIKit files, and add guidance for Crashlytics upload script
Remove interface
- Add a step to use mise (jdx/mise-action@v3) to install tuist 4.110.3 in all GitHub Actions workflows

Author: ducbm051291

.arkana.yml

@@ -1,4 +1,4 @@
-package_manager: cocoapods
+package_manager: spm
 environments:
   - Staging
   - Release

.github/wiki/Bitrise.md

@@ -9,7 +9,7 @@ Out of the box, the Bitrise Template has the following workflows and steps:
 |---------------------------|---------------------------------------------------------|-----------------------------------------|-------------------------------------------|
 | Git Clone Repository      | Git Clone Repository                                    | Git Clone Repository                    | Git Clone Repository                      |
 | Bitrise.io Cache:Pull     | Bitrise.io Cache:Pull                                   | Bitrise.io Cache:Pull                   | Bitrise.io Cache:Pull                     |
-| Run CocoaPods install     | Run CocoaPods install                                   | Run CocoaPods install                   | Run CocoaPods install                     |
+| Resolve SPM dependencies  | Resolve SPM dependencies                                | Resolve SPM dependencies                | Resolve SPM dependencies                  |
 | Fastlane - Build and Test | Xcode Test for iOS                                      | Xcode Test for iOS                      | Xcode Test for iOS                        |
 | Fastlane - Clean Up Xcov  | Fastlane Match                                          | Fastlane Match                          | Fastlane Match                            |
 | Danger                    | Fastlane - Build and Upload Production App to App Store | Fastlane - Build and Upload Staging App | Fastlane: Build and Upload Production App |
@@ -26,7 +26,7 @@ Out of the box, the Bitrise Template has the following workflows and steps:
 ## Environment and Secrets
 ### App Environtment Variables
 - BITRISE_PROJECT_PATH
-> e.g., ExampleApp.xcodeproj or in case you're using CocoaPod, it is ExampleApp.xcworkspace.
+> e.g., ExampleApp.xcodeproj.
 
 - TEAM_ID
 > This is your Apple Team ID (e.g., T3T4E84BAA), you can find it in `Membership` at Apple developer portal.
@@ -62,7 +62,7 @@ All four workflows have their own variables:
 > Final project directory structure
 ```
 ROOT
-├── ExampleApp.xcworkspace
+├── ExampleApp.xcodeproj
 ├── bitrise.yml
 ├──...
 ```

.github/wiki/CodeMagic.md

@@ -9,7 +9,7 @@ Out of the box, the CodeMagic Template has the following workflows and steps:
 | test                        | deploy_app_store                                        | deploy_staging_firebase                             | deploy_release_firebase                               |
 | --------------------------- | ------------------------------------------------------- | --------------------------------------------------- | ----------------------------------------------------- |
 | Install bundle              | Install bundle                                          | Install bundle                                      | Install bundle                                        |
-| Run CocoaPods install       | Run CocoaPods install                                   | Run CocoaPods install                               | Run CocoaPods install                                 |
+| Resolve SPM dependencies    | Resolve SPM dependencies                                | Resolve SPM dependencies                            | Resolve SPM dependencies                              |
 | Fastlane - Build and Test   | Fastlane - Build and Test                               | Fastlane - Build and Test                           | Fastlane - Build and Test                             |
 | Fastlane - Clean Up Xcov    | Fastlane Match                                          | Fastlane Match                                      | Fastlane Match                                        |
 | Fastlane - Build and deploy | Fastlane - Build and Upload Production App to App Store | Fastlane - Build and Upload Staging App to Firebase | Fastlane: Build and Upload Production App to Firebase |
@@ -52,7 +52,7 @@ Out of the box, the CodeMagic Template has the following workflows and steps:
 
 ```
 ROOT
-├── ExampleApp.xcworkspace
+├── ExampleApp.xcodeproj
 ├── codemagic.yaml
 ├──...
 ```

.github/wiki/Github-Actions.md

@@ -30,14 +30,14 @@ There are currently 4 workflows:
 ### Test
 
 1. Check out the current version.
-2. Install dependencies including Gem, Fastlane, and Cocoapods.
+2. Install dependencies via Bundler (Fastlane, Danger, etc.) and resolve SPM packages with Tuist/Xcode.
 3. Run Test on staging scheme and show result on pull request's check.
 
 ### Deploy
 
 1. Proceed to 4 if this job is running after `Test` job
 2. Check out the current version.
-3. Install dependencies including Gem, Fastlane, and Cocoapods.
+3. Install dependencies via Bundler (Fastlane, Danger, etc.) and resolve SPM packages with Tuist/Xcode.
 4. Install provisioning profiles and certificates using Fastlane match.
 5. Build archive version of the specified scheme.
 6. Deploy to Firebase Distribution, TestFlight, or App Store.

.github/wiki/Project-Dependencies.md

@@ -3,18 +3,13 @@ To simplify setup for developers new to the application, as well as having a rel
 The project normally contains:
 
 - Fastlane: is the easiest way to automate beta deployments and releases for the `iOS` (also `Android`) applications. 🚀 It handles all tedious tasks, such as generating screenshots, dealing with code signing, and releasing the application.
-- Cocoapods: manages dependencies for Xcode projects. Cocoapods aims to improve the engagement with, and discoverability of, third-party open-source Cocoa libraries. Developers only need to specify the dependencies in a file named `Podfile`. Cocoapods recursively resolves dependencies between libraries, fetches source code for all dependencies, and creates and maintains an Xcode workspace to build the project.
-- Swift Package Manager: a tool for managing the distribution of Swift code. It’s integrated with the Swift build system to automate the process of downloading, compiling, and linking dependencies.
+- Swift Package Manager: the single source of truth for runtime dependencies. All shared libraries are declared in `Project.swift` and appear in Xcode's **Package Dependencies** section.
 
 ## Dependencies
 
 ### Bundler
 
-[Bundler](https://bundler.io/) is a Ruby package manager, think of it as a Cocoapods for ruby plugins that will be used for the project. Keeping package versions the same on all development machines and Continuous Development machines reduces unnoticed bugs from occurring. Noteworthy packages include `Fastlane`, `Firebase-cli`, and `Cocoapods`.
-
-### Cocoapods
-
-[Cocoapods](https://cocoapods.org/) manages iOS packages to keep consistency throughout development machines.
+[Bundler](https://bundler.io/) is a Ruby package manager used for CLI tooling such as `fastlane`, `xcov`, and `danger`. Keeping package versions the same on all development machines and Continuous Development machines reduces unnoticed bugs from occurring.
 
 ### Fastlane
 
@@ -30,29 +25,17 @@ The main usage of [Firebase](https://firebase.google.com/) for our team is `Fire
 
 [Alamofire](https://github.com/Alamofire/Alamofire) is a networking library for Swift projects. Alamofire is used as a base for our Networking layer to streamline API calls in all projects, allowing developers to switch between projects without an issue.
 
-### SnapKit (pre-SwiftUI)
-
-[SnapKit](https://github.com/SnapKit/SnapKit) is the tool for layout user interface with ease and easier to establish a team's convention. SnapKit applies Auto Layout using a more concise syntax. This allows the UI to be responsive on different devices.
-
-### RxSwift
-
-[RxSwift](https://github.com/ReactiveX/RxSwift) is the library for writing Swift in the reactive programming way. RxSwift added a reactive framework for Swift with syntax closely resembling other Rx frameworks. Although it is possible to implement reactive programming for Swift, RxSwift can bypass problems that arise from maintaining large plugins and allow developers from other platforms to easily understand RxSwift syntax.
-
-### IQKeyboardManagerSwift
-
-[IQKeyboardManager](https://github.com/hackiftekhar/IQKeyboardManager) is a plugin for `UIScrollView`. IQKeyboardManager will detect when the keyboard is showing and adjust the view so that the view is not blocked by the keyboard. IQKeyboardManager is the go-to solution because of the ease of installation and history of maintenance by the developers.
-
 ### SwiftLint
 
-[SwiftLin](https://github.com/realm/SwiftLint) is used to enforce our team's code convention. SwiftLint is the perfect tool for this task as it is customizable, lightweight, and automate-able. Our team installs SwiftLint with `Ruby` to allow Continuous Integration machine capability to replicate local lint. SwiftLint is integrated with Xcode to display a warning and halt build when error.
+[SwiftLint](https://github.com/realm/SwiftLint) is used to enforce our team's code convention. SwiftLint is the perfect tool for this task as it is customizable, lightweight, and automate-able. CI installs SwiftLint via Homebrew, and Danger runs it directly (no Pods required).
 
 ### KeychainAccess
 
 [KeychainAccess](https://github.com/kishikawakatsumi/KeychainAccess) is a wrapper for Keychain, making storing data with Apple's encryption as convenient as using `UserDefault`.
 
 ### Sourcery
 
-Swift code generator running on top of Stencil. [Sourcery](https://github.com/krzysztofzablocki/Sourcery) is used to generate Protocol's Mock for Unit Testing purposes. We include Sourcery in `podfile` and add a shell script to Xcode Build Phrase `./Pods/Sourcery/bin/sourcery`.
+Swift code generator running on top of Stencil. [Sourcery](https://github.com/krzysztofzablocki/Sourcery) is used to generate Protocol mocks for Unit Testing purposes. The template vendors Sourcery via scripts and runs it from `Scripts/Swift/iOSTemplateMaker`.
 
 ### SwiftFormat
 

.github/workflows/test_swiftui_install_script.yml renamed to .github/workflows/test_install_script.yml

@@ -1,4 +1,4 @@
-name: Test SwiftUI Install Script
+name: Test Install Script
 
 on:
   push:
@@ -15,11 +15,14 @@ jobs:
     steps:
     - uses: actions/checkout@v6
 
+    - name: Install tools with mise
+      uses: jdx/mise-action@v3
+
     - name: Bundle install
       run: bundle install
 
-    - name: Start Install Script for SwiftUI Template App
-      run: swift run --package-path Scripts/Swift/iOSTemplateMaker iOSTemplateMaker make --bundle-id-production co.nimblehq.ios.templates --bundle-id-staging co.nimblehq.ios.templates.staging --project-name TemplateApp --interface SwiftUI
+    - name: Start Install Script for Template App
+      run: swift run --package-path Scripts/Swift/iOSTemplateMaker iOSTemplateMaker make --bundle-id-production co.nimblehq.ios.templates --bundle-id-staging co.nimblehq.ios.templates.staging --project-name TemplateApp
 
     - name: Build and Test
       run: bundle exec fastlane buildAndTest

.github/workflows/test_uikit_install_script.yml

@@ -52,17 +52,11 @@ jobs:
     - name: Bundle install
       run: bundle install
 
-    - name: Cache Pods
-      uses: actions/cache@v4
-      id: cocoapodCache
-      with:
-        path: Pods
-        key: ${{ runner.os }}-pods-${{ hashFiles('**/Podfile.lock') }}
-        restore-keys: |
-          ${{ runner.os }}-pods-
+    - name: Install tools with mise
+      uses: jdx/mise-action@v3
 
     - name: Start Install Script for Template App
-      run: swift run --package-path Scripts/Swift/iOSTemplateMaker iOSTemplateMaker make --bundle-id-production co.nimblehq.ios.templates --bundle-id-staging co.nimblehq.ios.templates.staging --project-name TemplateApp --interface UIKit
+      run: swift run --package-path Scripts/Swift/iOSTemplateMaker iOSTemplateMaker make --bundle-id-production co.nimblehq.ios.templates --bundle-id-staging co.nimblehq.ios.templates.staging --project-name TemplateApp
 
     - name: Start Setup Script for Template App Firebase Upload
       run: swift run --package-path Scripts/Swift/iOSTemplateMaker iOSTemplateMaker make-test-firebase

.github/workflows/test_upload_build_to_firebase.yml

@@ -26,6 +26,9 @@ jobs:
       with:
         fetch-depth: 0
 
+    - name: Install tools with mise
+      uses: jdx/mise-action@v3
+
     - name: Install SSH key
       uses: webfactory/[email protected]
       with:
@@ -34,17 +37,17 @@ jobs:
     - name: Bundle install
       run: bundle install
 
-    - name: Cache Pods
+    - name: Cache SPM Packages
       uses: actions/cache@v4
-      id: cocoapodCache
+      id: spmCache
       with:
-        path: Pods
-        key: ${{ runner.os }}-pods-${{ hashFiles('**/Podfile.lock') }}
+        path: .build
+        key: ${{ runner.os }}-spm-${{ hashFiles('**/Package.resolved') }}
         restore-keys: |
-          ${{ runner.os }}-pods-
+          ${{ runner.os }}-spm-
 
     - name: Start Install Script for Template App
-      run: swift run --package-path Scripts/Swift/iOSTemplateMaker iOSTemplateMaker make --bundle-id-production co.nimblehq.ios.templates --bundle-id-staging co.nimblehq.ios.templates.staging --project-name TemplateApp --interface UIKit
+      run: swift run --package-path Scripts/Swift/iOSTemplateMaker iOSTemplateMaker make --bundle-id-production co.nimblehq.ios.templates --bundle-id-staging co.nimblehq.ios.templates.staging --project-name TemplateApp
 
     - name: Start Setup Script for Template App TestFlight Upload
       run: swift run --package-path Scripts/Swift/iOSTemplateMaker iOSTemplateMaker make-test-test-flight

.github/workflows/test_upload_build_to_test_flight.yml

@@ -43,14 +43,6 @@ xcuserdata/
 *.xcscmblueprint
 *.xccheckout
 
-# CocoaPods
-#
-# We recommend against adding the Pods directory to your .gitignore. However
-# you should judge for yourself, the pros and cons are mentioned at:
-# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
-#
-Pods/
-
 # fastlane
 #
 # It is recommended to not store the screenshots in the git repo.
@@ -74,6 +66,7 @@ Output
 
 # Tuist
 .tuist-generated
+*.xcworkspace
 
 # JetBrains IDEs