Supermind creation flow

<!---
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
--->
* Allow users to create Supermind requests to send to other users.
* Supermind requests are when a user offers another user tokens or cash to reply to their post.

## 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.
--->
* Users can create SuperMind requests via a number of entry points.
  * Via an activity post (in-feed or post entity)
  * Via a channel (by clicking `SuperMind` within the header)
  * Via the composer (when creating a post and toggling SuperMind)

**Create Request Flow from Composer**

* Regardless which entry point a user tags, the proceeding flow is the same. The workflow when creating a SuperMind request is outline within the following prototype and detailed below.
  * The compose will launch. The SuperMind badge will appear top-right. Note also the slight change in context of the composer toolbar.
    * Monetise has been removed
    * The post button has been replace with a continue button.
    * \[Confirm which options to be omitted from the ellipsis menu\]
  * When a user presses continued, they will be brought to the SuperMind screen. Here the user can confirm the targeted channel, define an offer amount and currency type.
    * A user can pay in either tokens or cash.
    * A user can only pay in cash where the producer has a bank account connected to their minds account.
    * Where the producer does not have a connected bank account, the consumer will not see a cash option
  * When a SuperMind request is made, there are a total of four response types. There are:
    * Any reply (Text)
    * Video Reply
    * Image Reply
    * Remind
  * It is assumed that Twitter integration will not be required for the first iteration.
  * Where a minimum offer value is present, a user can not submit a request where the minimum offer has not be satisfied.
  * Once the user presses ‘Send Request’ a notice will display informing them that the request has been sent and when to expect a reply.

**Create Request from Activity Post in Feed**

* A new `S` SuperMind icon is to appear within the activity post interactions, replacing tip. Tip is to be moved within the ellipsis menu.
* After clicking on the SuperMind prompt, the the composer will launch with the quoted post in-view.
* Additionally, we may want to draw attention to the `SuperMind` button within the activity post (feed).
  * Where a user interests with a post (i.e. up-vote) we could highlight the SuperMind button my means of a popover.
  * See proposed flow here -> **[Supermind Init via post - prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=303%3A9795&viewport=-9081%2C5560%2C1&scaling=min-zoom&starting-point-node-id=303%3A9795&show-proto-sidebar=1)**

**Via the Composer**

* Additionally users may create SuperMind requests from within the composer, without being referred from a post or from within the channel.
* Note the inclusion of the new `S` / SuperMind icon with the composer toolbar.
  * As the user types, if they enter a valid channel name, attention should be brought to the `S` icon with a tooltip.
  * Clicking the `S` will lunch the SuperMind screen, where they can define the target, currency type, bid etc.
  * Alternatively the user can simply open the SuperMind menu without necessarily specifying a channel name within the composer itself.
* See prototype here -> **[Supermind init via composer - prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=447%3A14608&viewport=-9081%2C5560%2C1&scaling=min-zoom&starting-point-node-id=447%3A14608&show-proto-sidebar=1)**

**Via the channel**

* Supermind CTA will only appear when viewing someone else's channel. See prototype below.
* **[Supermind init via channel - prototype](https://www.figma.com/proto/thrGepQAxmcMGB7MoEEckM/Supermind?page-id=287%3A5127&node-id=303%3A9203&viewport=2397%2C-4957%2C0.5&scaling=min-zoom&starting-point-node-id=303%3A9203&show-proto-sidebar=1)**

## 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
--->

- [ ] See: https://gitlab.com/minds/front/-/issues/5713

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 8.0