Convert more fastlane tools to swift commands (#5163)

* Upload dSYMs to sentry using swift and the sentry-cli instead of fastlane.

* Replace the fastlane `config_production` lane with a swift tools `ConfigureProduction` command.

* Replace Zsh with CI.run in the new ConfigureNightly command

* Replace the fastlane `tag_nightly` lane with a swift tools `TagNightly` command.

* Print out all the commands going through CI.Run and their arguments

* Address PR comments

ci_scripts/ci_common.sh

@@ -30,7 +30,7 @@ setup_xcode_cloud_environment () {
 }
 
 install_xcode_cloud_brew_dependencies () {
-    brew update && brew install xcodegen pkl
+    brew update && brew install xcodegen pkl getsentry/tools/sentry-cli
 }
 
 setup_github_actions_environment() {

ci_scripts/ci_post_clone.sh

@@ -12,5 +12,5 @@ elif [ "$CI_WORKFLOW" = "Element Pro" ]; then
     # Xcode Cloud automatically fetches the submodules.
     swift run pipeline configure-element-pro
 else
-    bundle exec fastlane config_production
+    swift run pipeline configure-production
 fi

ci_scripts/ci_post_xcodebuild.sh

@@ -9,7 +9,7 @@ fetch_unshallow_repository
 
 # Upload dsyms no matter the workflow
 # Perform this step before releasing to github in case it fails.
-bundle exec fastlane upload_dsyms_to_sentry dsym_path:"$CI_ARCHIVE_PATH/dSYMs"
+swift run -q tools upload-dsyms --dsym-path "$CI_ARCHIVE_PATH/dSYMs"
 
 generate_what_to_test_notes
 
@@ -17,5 +17,5 @@ if [ "$CI_WORKFLOW" = "Release" ]; then
     bundle exec fastlane release_to_github
     bundle exec fastlane prepare_next_release
 elif [ "$CI_WORKFLOW" = "Nightly" ]; then
-    bundle exec fastlane tag_nightly build_number:"$CI_BUILD_NUMBER"
+    swift run -q tools ci tag-nightly --build-number "$CI_BUILD_NUMBER"
 fi