CP Mobile-Expensify PRs

[roryabraham]

HOLD on #58775

Problem

HybridApp includes code from two repos - E/App and E/Mobile-Expensify. If something is broken on HybridApp staging, and we need code changes in E/Mobile-Expensify to fix it, we don't have great options:

• deploy all the code on Mobile-Expensify main. Not ideal because it may introduce unrelated changes which might create other unforeseen issues
• manually cherry-pick changes to the Mobile-Expensify staging branch, then merge a dummy PR in E/App to trigger a deploy. Not ideal because it's non-obvious, error prone, and involved merging unrelated changes in E/App.

Solution

Update the cherryPick.yml workflow to enable cherry-picking pull requests to staging from either E/App or E/Mobile-Expensify

[melvin-bot]

Triggered auto assignment to @abekkala (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details. Please add this Feature request to a GH project, as outlined in the SO.

[melvin-bot]

⚠️ It looks like this issue is labelled as a New Feature but not tied to any GitHub Project. Keep in mind that all new features should be tied to GitHub Projects in order to properly track external CAP software time ⚠️

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @dannymcclain (NewFeature)