NSQS Frontend components: NSQS setup (OAuth Flow)

[yuwenmemon]

This all will be implemented behind the nsqs beta.

---

Tracking Issue: https://github.com/Expensify/Expensify/issues/446352

Design Doc Section: https://docs.google.com/document/d/18g8cUtqiSwJce2a42d7uU1dLmxz6hjfVf1bIXwyz4PY/edit?tab=t.0#heading=h.jjgspdksgmgz

---

NSQS setup (OAuth Flow)

This is going to be a straightforward basic page NSQSSetupPage that renders a form using FormProvider.

Issue Owner

Current Issue Owner: @

Issue Owner

Current Issue Owner: @s77rt

[melvin-bot]

Current assignee @s77rt is eligible for the External assigner, not assigning anyone new.

[melvin-bot]

Triggered auto assignment to @stephanieelliott (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 - @shawnborton (NewFeature)

[melvin-bot]

This issue has not been updated in over 15 days. @yuwenmemon, @s77rt, @ikevin127 eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[s77rt]

@yuwenmemon Can we close this?

[s77rt]

or I think @ikevin127 requires payment here?

[yuwenmemon]

I believe payment for @ikevin127 is being handled in a different issue: #55495 (comment)

So this should be good to close!