Build console to manage Superminds

<!---
Please read this!

The Definition of Ready (DoR) can be found at https://developers.minds.com/docs/handbook/how-we-work/#definition-of-ready-dor

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Type::Feature" label and verify the feature you're about to submit isn't a duplicate.
--->

## Goal

<!---
Clearly outline the goal of the issue and why we are doing it
--->
- Create management console for users to easily accept and respond to Supermind requests or reject them


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

*Note: All design links below refer to the web UI.*

**[Supermind Console Prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=1045%3A20853&viewport=4819%2C-9298%2C1&scaling=min-zoom&starting-point-node-id=1045%3A20853)**

* The SuperMind (console) is accessible via the `More Menu` within the main navigation.
* Users will also be directed here from email and push notifications.
* This SuperMind console is separate from the Boost console.
  * This console displays only the incoming requests [Requests received](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=319%3A12073)
  * And outgoing requests [Requests sent](https://www.figma.com/file/thrGepQAxmcMGB7MoEEckM/Supermind?node-id=338%3A12739)
* The settings icon contained within the above designs will link directly to the SuperMind settings (within the Settings Area).

**Requests Received**

* A user may either reply to a request, or choose to reject it.
* A producer has \[72 hours\] to respond to a request.
* Any expired request will disappear from `Requests Received`
* Requests are ordered from new -> old.
* Each request will also display any meta data relevant to the request.
  * Offer amount
  * Twitter post
  * Content type: Text, Video, Image, Remind.
* If the user clicks reject, funds are refunded to the consumer and a notification sent (As detailed within notification)
* Where the user clicks reply, the composer is launched.
  * Note: If the is the users first-time replying to a SuperMind request, they will need to read and agree to the relevant terms of user.
  * After doing so, they’ll then be directed to the composer.
  * If there’s there are specific content requirements, this could be communicated within the placeholder copy. (e.g. video required).
* Workflow for the above detailed here -> [Accept request workflow with T&Cs](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=319%3A12073&viewport=857%2C575%2C0.13&scaling=min-zoom&starting-point-node-id=319%3A12073)

## Personas

<!---
Who does this user impact and why (optional)
--->


## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] ...

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0