feat: add workflow for updating automated test results in TestRail

[chrisleewilcox]

Description

Adding a workflow to release_e2e_pipeline to post test results to TestRail. This initial implementation will focus on utilizing TestRail API to post test results to TestRail mobile project when all workflows in the bitrise release_e2e_pipeline are successful. Test results will not be posted if any other workflow fails on the release_e2e_pipeline with this implementation.

Automated Test Cases in TestRail will need to be reviewed and updated to ensure the most accurate reporting until we implement mapping of automated scripts to automated test cases in TestRail. Once a mapping mechanism has been implemented this will allow us to report failed test runs in a more effective manner.

Not able to run the pipeline from bitrise dashboard until this PR is merged. Test runs for this PR was done using curl command shared in the bitrise advanced modal for the pipeline.

• need auth token for bitrise

Related issues

Fixes: https://github.com/MetaMask/mobile-planning/issues/1891

Manual testing steps

1. on bitrise MetaMask mobile project run release_e2e_pipeline on release branch
2. all workflows on release_e2e_pipeline are successful
3. test results from pipeline are posted to TestRail mobile project
4. Test Run is created in TestRail will all automated test cases status is Passed

Screenshots/Recordings

Before

No workflow to save test results in TestRail

After

Failed pipeline doesn't post test results: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/4047bd66-20a1-405b-bd9d-c3e03942bc5a?tab=workflows

Pipeline with disabled workflows: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/961a7743-e820-4a8a-bcd8-a836c4babb48?tab=workflows

Successful pipeline post test results:

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.

[cortisiko]

🌮 🌮 🌮

[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