[match] profile name parameter to specify your own provisioning profile name

[josherbushel]

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

The default provisioning profile names can sometimes exceed Apple's allowed length (50 characters). While this works, transferring an app to a different account can cause long profile names to become hidden and thus unable to be deleted. It'd be nice to specify your own custom profile name as you/your company could create your own naming format and/or trim long names to Apple's allowed length.

Description

I added a profile_name parameter to the Match tool. If this is specified, it will use that instead of the default provisioning profile. I added the option in options.rb and modified the generator.rb. I tested it by running fastlane match --profile_name "Your Profile Name". Below is a video of how it works. First command is just the default.
https://www.dropbox.com/s/7m7ordts0d9pczo/FastlaneProfileName.mov?dl=0

Testing Steps

Run fastlane match --profile_name "Your own profile name" in the terminal, or add profile_name parameter in the fastfile.

[googlebot]

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.

[josherbushel]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[craigomac]

Thanks for this PR—it'll solve an issue we're experiencing where we have a "hidden" provisioning profile with the name Match wants to use. Apple won't remove it (we've tried asking).

[fastlane-bot]

Hey @josherbushel 👋

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.147.0 🚀