Use fastlane lane for match in Bitrise workflows

[blyscuit]

Issue

Current Bitrise workflow uses Bitrise Fastlane Match to run fastlane match.
This is different from GitHub Actions and local run and can cause issue if the implementation in fastfile diverge.

Solution

• Use lane declared in fastfile to run fastlane match.
• sync_adhoc_signing, sync_adhoc_production_signing, sync_appstore_signing.
• Need to add update_code_signing_settings to fastfile from Modify signing automatically when generating a project #330 to automatically change settings on Xcode.

Who Benefits?

Bitrise users and iOS Template maintainers.

[suho]

We should use our lanes that declared in the Fastfile :D

[blyscuit]

This is ready to work on. Since it is a good first issue, we can leave it for dev starting in this repo.