[Fastlane.Swift] Swift fastlane does not run on Apple Silicon

[kikeenrique]

• [Swift] Add test with fixture to check fastlane swift upgrades.

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I've read the Contribution Guidelines
• I've updated the documentation if necessary.

Motivation and Context

Adds swift fastlane tests that:

• will check problems on Fastlane swift project upgrades.
• will check Fastlane swift project compilation and runtime problems. It will fail in mac M1 until Swift fastlane does not run on Apple Silicon #18502 is merged.

Description

• Add a fastlane swift project fixture, based on fastlane v2.198. The project also implements a simple "custom" lane.
• Add a extra step to generate_swift_api
• Add --enable_runner_upgrades parameter to allow auto accept changes on fastlaneRunner upgrades.

Testing Steps

Executing bundle exec fastlane generate_swift_api

[minuscorp]

We shouldn't add the code duplicated as a fixture, this is unmaintainable in the long run, this should be closed and use the other PR better.
Add the improvements to the other PR, like the flag and so on.

[kikeenrique]

How would you test then swift project upgrades?
My intention would not be to upgrade fixtures, they will be use to test project upgrades from each version.
Every modification in fastlane runner xcode project should be updated in fastlane runner project, and you can't foresee when a user will update versions.

[minuscorp]

Maintenance of Swift is made when there're requirements for it, it makes no sense to use a fixture because it wouldn't be the real code when somebody makes a change if you are using a static version of all the runner and the project itself. The flag and the other changes are good to add in the other PR.