chore: Bump deploy to bitrise step to 2.2.3

[Cal-L]

Description

Bitrise requires that we bump the deploy-to-bitrise step to 2.0.0 or higher by a certain date. This task bumps the ones that are using major version 1.

Deploy to bitrise step - https://bitrise.io/integrations/steps/deploy-to-bitrise-io

Related issues

Fixes:

Manual testing steps

build_ios_release and build_ios_flask_release will continue to work. We can trust that the step works since we're already using 2.2.3 everywhere else.

Screenshots/Recordings

Before

After

Pre-merge author checklist

• I’ve followed MetaMask Contributor Docs and MetaMask Mobile Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[MarioAslau]

Looks good to me !