[gym] improved provisioning export with odd names in specs

[hfehrmann]

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

Gym provisioning profile resolution for exporting the ipa when detecting profiles from project is not clear in the documentation.

Description

Gym detects by default the provisioning profiles. The documentation states that it is possible to define the export provisioning profiles. However, the actual resolution is consistent with the specs of CodeSigningMapping. This MR only clarifies the spec for the mapping.

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[hfehrmann]

@googlebot I signed it!

[joshdholtz]

These PRs are some of my favorite 😊 Your changes make it much clearer with what is being tested! Thank you ❤️ Appreciate the contribution!

[hfehrmann]

@joshdholtz I'm glad you liked it 😁. I also want to change the documentation for the specific part of provisioning profile export, but I don't know where to do it. I had some problemas with how things work, because the name of my profiles are "non-standard", and gym behaved weird from my perspective. That behavior lead to improve this part of the spec, which actually behaves as expected per the spec, but it is not clear to the final user.

[fastlane-bot]

Hey @hfehrmann 👋

Thank you for your contribution to fastlane and congrats on getting this pull request merged 🎉
The code change now lives in the master branch, however it wasn't released to RubyGems yet.
We usually ship about once a week, and your PR will be included in the next one.

Please let us know if this change requires an immediate release by adding a comment here 👍
We'll notify you once we shipped a new release with your changes 🚀

[fastlane-bot]

Congratulations! 🎉 This was released as part of fastlane 2.184.1 🚀