[match] add git authentication methods to match import command

[rb1193]

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.

Unfortunately two tests are failing for reasons I don't understand - possibly fastlane is caching the auth credentials somewhere?

Failed examples:
rspec ./fastlane/spec/actions_specs/import_from_git_spec.rb:162 # Fastlane Fastlane::FastFile import_from_git with caching works with new tags
rspec ./fastlane/spec/actions_specs/import_from_git_spec.rb:200 # Fastlane Fastlane::FastFile import_from_git with caching works with branch

Motivation and Context

Similar to #18202 but for fastlane match import. I've been attempting to upload new certs, keys and provisioning profiles using basic authorization but that's not possible because the git_basic_authorization parameter is not available when using match import

Description

Added the git_private_key, git_basic_authorization and git_bearer_authorization parameters to the match import storage client

Testing Steps

Use fastlane match import with the --git-basic-authorization parameter set

[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.

[rb1193]

@googlebot I signed it!

[joshdholtz]

Ooops, can’t believe this was forgotten 😱 Thank you for adding this! Really appreciate it ❤️

[fastlane-bot]

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