Update contact picker in submit expense flow

[dubielzyk-expensify]

Problem

From our recent usability studies and other observations we can see that people are struggling to submit to the right place.

Solution

Given most people would wanna submit to a workspace let's make a seperate section at the top for the workspaces that the user can submit to and also show who the approver would be:

Everything else remains the same

cc @Expensify/design @trjExpensify @JmillsExpensify

[melvin-bot]

Triggered auto assignment to @sakluger (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 - @dubielzyk-expensify (NewFeature)

[melvin-bot]

Current assignee @sakluger is eligible for the NewFeature assigner, not assigning anyone new.

[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 - @shawnborton (NewFeature)

[melvin-bot]

Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.

[trjExpensify]

Oh, Is this for the participant selector in the Submit expense flow? If so, we're in the process of killing that now (and Track expense) as the A/B test of a consolidated Create expense performed better.

For Create expense we have this PR in review already for the updates in this issue.

[dubielzyk-expensify]

It could be for Create expense too. I think we should probably merge the two mocks then?

[dannymcclain]

Yeah I think we should just update this recipient screen for any/all expense flows.

[shawnborton]

Definitely agree there

[shawnborton]

I think the PR above does cover all the cases though, at least that's what it seemed like from running a quick test.

[trjExpensify]

Yeah, so maybe for a follow-up PR with this issue, we can switch out Workspace for the submitsTo on the workspace rows?

[dubielzyk-expensify]

Sounds good 👍 So which issue do we keep?

[trjExpensify]

We can keep the other linked to the PR. I've added that to the OP:

[sakluger]

I'm going to add this to the #convert project since it has to do with new customer adoption. Let me know if it should live elsewhere.