fix: correct RC build workflows to use RC configurations instead of prod

[sethkfman]

Description

This PR fixes the RC (Release Candidate) build workflows in bitrise.yml that were incorrectly using production build configurations instead of the appropriate RC configurations.

What is the reason for the change?
The RC build workflows and were calling production build steps ( and ) instead of the RC-specific build steps.

What is the improvement/solution?
Updated the workflows to use the correct RC build configurations:

• now calls build_android_main_rc
• now calls build_ios_main_rc

Also removed obsolete TODO comments that were no longer relevant.

Changelog

CHANGELOG entry: null

Related issues

Fixes: N/A

Manual testing steps

1. Trigger an RC build via Bitrise
2. Verify that the RC build uses the correct RC configurations
3. Confirm that the generated apps have RC-specific settings

Screenshots/Recordings

N/A - Build configuration changes only

Before

RC builds were using production configurations

After

RC builds now use the correct RC configurations

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

[metamaskbot]

Missing release label release-7.52.0 on PR. Adding release label release-7.52.0 on PR and removing other release labels(release-7.53.0), as PR was cherry-picked in branch 7.52.0.