Refactor Requests page

[tcp]

What?

Refactor the pages under /requests.

Why?

We have some updated content in Figma that should see the light of day asap. The entire flow needs to be reworked; it needs tests, we need to double check the routes and if we're showing the right information. In addition, there's a great chance for componentizing the requests pages.

Breakdown

• Write e2e tests for /requests
• Check if all routes being used are correct
• Check if the contents being displayed are correct (e.g. current budget != requested budget)

Additional Context

I'll leave space here for a better breakdown when this issue is underway.