giseldo/neodataset huggingface dataset:
Implement default for heading and body available for Text component

<!---
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

Implement default for heading and body available for Text component

## What needs to be done

- extend Text component with categories to support headings and body for both themes

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## Personas

Developers

## 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
Add color palette and theme colors.

<!---
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

Add color palette and theme colors to design system.


## What needs to be done

- define the independent colors and the themes colors as per design system.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## Personas

Developers

## 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: 3.0
Add Inter fonts, typography and layout configuration as per Design System

<!---
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

Add Inter fonts, typography and layout configuration as per Design System 


## What needs to be done

- add Inter font to project and config
- add config for typography as per design system.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## Personas

Developers

## 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: 3.0
Create separate module for the design system as per Tamagui guidelines

<!---
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

Create new Minds design system.

## What needs to be done

- create separate module for the design system as per Tamagui guidelines
- install Tamagui core and default basic configuration
- add separate entry point to App.ts for implementing components under the new design system


## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

- [Minds design system](https://www.figma.com/file/EkJej3mKP2lSzmWTLoqlXD/Minds-Design-System?node-id=59%3A2&t=y87OMAD6MnCx98qa-0)

## Personas

Developers


## 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: 8.0
SPIKE: Evaluate Nitro build process in github CI/CD.

<!---
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

Reduce the build time of the native applications for the store releases on both iOS and Android.

## What needs to be done

- make sure the github repo is in sync with the gitlab repo
- implement github actions as per Nitro [documentation](https://docs.nitro.build/docs/ci/github-actions).
- the API key: e9af9194-1d6f-40f6-994e-0a9700779acf

## 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.
--->


## 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
Supermind settings minimum values should be pulled from config

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

Min Supermind values aren't taken from config in Supermind settings - this means that now the engine is being updated for https://gitlab.com/minds/engine/-/merge_requests/1188, mobile does not reflect these changes (see screenshot)

### Steps to reproduce

1. Point at either the branch for https://gitlab.com/minds/engine/-/merge_requests/1188 or whatever env that change is released to.
2. Go to Supermind settings and try to set a value of 1 for cash. 

### Platform information 

Mobile

### What is the current *bug* behavior?

Shows a $10 min when config states it should be 2.

### What is the expected *correct* behavior?

Should update based upon config.

### Relevant logs and/or screenshots

![image](/uploads/88db2534c2f40a05c3a87921a7f1ff48/image.png)

### Possible fixes

It appears to be hardcoded here:

https://gitlab.com/minds/mobile-native/-/blob/f598d0419d482d58867a085fd33f316db481e089/src/settings/screens/SupermindSettingsScreen.tsx#L144

Value can be grabbed from https://www.minds.com/api/v1/minds/config (upermind.min_thresholds.min_cash / min_usd)

![image](/uploads/0f3ea9ed2a64d2510833c58a5058737c/image.png)

Story points: 2.0
Submit new build to Apple Store

<!---
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

Get the iOS build publish.

## What needs to be done

- hide behind the flag the supermind icon in the post toolbar.
- hide behind the flag the payment item in Settings.

![image](/uploads/5d35424ff1ceb6c05570282c88c5e600/image.png)
![image](/uploads/0ec7de0efb0307f91d415fbcbaefe719/image.png)

## 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.
--->


## Personas

Developers

## 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: 2.0
Notifications refresh when tapping the tab is broken



### Summary

The notifications list is not refreshed when pressing the tab

### Steps to reproduce

Open the notifications screen and press the tab again

### Platform information 
both

### What is the current *bug* behavior?

It doesn't refresh

### What is the expected *correct* behavior?

it should refresh the llist

### Relevant logs and/or screenshots

-

### Possible fixes
-

Story points: 1.0
Nothing happens when "Connect wallet" is clicked

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

In Wallet > Token > Settings, there is a button to connect wallet, but nothing happens when it's clicked.

### Steps to reproduce

1. Go to Wallet > Token > Settings
2. Click connect wallet (or change wallet)
3. See that nothing happens
4. (video bellow)

### Platform information 

iOS, Android

### What is the current *bug* behavior?

Nothing happens when clicking the button.

### What is the expected *correct* behavior?

The button should not be in either app

### Relevant logs and/or screenshots

![XRecorder_21112022_224622](/uploads/45359f6e25b45e691ef0c49281b06ed0/XRecorder_21112022_224622.mp4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
User freebird22 is subscribed to 7 users, but only 3 show on mobile devices

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

User freebird22 is subscribed to 7 users, but only 3 show on mobile devices (and only 5 show on desktop - my guess is that the two that arent visible on desktop might be Minds channel, and a channel that was deleted?)

### Steps to reproduce

1. Go to users freebird22 profile, and click subscriptions
2. See that there are only three channels

### Platform information 

iOS and Android

### What is the current *bug* behavior?

Only 3 subscriptions show for the user

### What is the expected *correct* behavior?

More subscriptions should show for the user

### Relevant logs and/or screenshots

![image](/uploads/7804bde7f401a49ca9a938da4224b3ed/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 3.0
Mobile: Build out new boost 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 for users to create a boost that can run over multiple days

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Build out components and the flow as per the UX mockups and flows. 

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->
See flows. 

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->
Mockups provided in https://gitlab.com/minds/design/-/issues/69


## Personas

<!---
Who does this user impact and why (optional)
--->
Boosters

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->
Yes

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] Implementation of UI components and flow as per UX mockups
- [ ] Experiment flag is setup 
- [ ] E2E tests

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Remove Minds+ and Superminds from iOS deploy

<!---
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

Apple rejected the latest submission due to latest updates in Developers Guide. 
Get the latest iOS app approved by apple by removing the Minds+ and Superminds from the app.

## What needs to be done

Branch from `master` as HotFix

Only for iOS
- remove Minds+ from the drawer
- remove Superminds from the drawer
- remove other Minds+ and Superminds visible references 
- preserve accepting Superminds and boosts.

## 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.
--->


## Personas

Developers

## 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

- [ ] No Minds+ in drawer
- [ ] No Supermind in drawer

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Remoe

Story points: 3.0
The bottom navigation overlaps over some of the controls

<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "T - Bug" label and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

The bottom navigation overlaps over some of the controls. I opened a post in the testflight 4.30, and the upvote etc buttons were cropped. Something similar happened with a cancel button

![image](/uploads/814944ec7bbb6ae0f6376940988ea094/image.png)

### Steps to reproduce

1. Get new testflight version of the app.
2. Open a post from newsfeed
3. See that the menu navigation overlaps buttons


### Platform information

iOS 4.30

### App version

4.30

### What is the current *bug* behavior?

The buttons are being overlapped by the bottom navigation

### What is the expected *correct* behavior?

Bottom navigation should not show in those cases

### Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Error message is unclear when accepting a supermind offer that is looking for image or video replies

### Summary

Error message should be clear that you need to upload an image or a video when accepting a supermind offer that expects an image or a video. 

### Steps to reproduce

1. Login as user1. 
2. Send a supermind offer with image/video reply to user2. 
3. Login as user2.
4. Accept the offer.
5. Do not add image/video in supermind reply.
6. Press send.
7. Error message appears that is not descriptive. 

### Platform information 

4.30 RC - Browserstack S22

### What is the current *bug* behavior?

Error message is not clearly explaining why supermind is not working. 

### What is the expected *correct* behavior?

Error message should be clear as in web. Please follow similar text as web. 

### Relevant logs and/or screenshots

![image](/uploads/55c5abef9d9ac021ecc7d7fc127b05a2/image.png)

Story points: 2.0
Cancel button is getting truncated for Superminds

### Summary

Cancel button is not visible on superminds confirmation modals. 

### Steps to reproduce

1. Open app. 
2. Login as a user and send superminds. 
3. On confirm modal, notice cancel button truncated. 
4. Same issue when accepting a superminds. 

### Platform information 

Browserstack 4.30 RC - S22

### What is the current *bug* behavior?

Cancel button is truncated

### What is the expected *correct* behavior?

Cancel button should be visible. 

### Relevant logs and/or screenshots

![image](/uploads/1c68ce05fc1705eb9f6a3c62865004f4/image.png)

![image](/uploads/ed160a0ca7ed6d70a0e7a9a3f2a9ab97/image.png)

Story points: 1.0
Stripe Flow: Adding a Card

<!---
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
--->

Adding a card should use the new Stripe flow

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

Add a card from CardSelector should open Stripe and redirect back to the card selector with the newly created card 

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

Make sure you can add a card by moving to the stripe website.

## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

N/A

## 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
--->

- [ ] Given I'm on supermind compose screen
- [ ] And I select the cash option
- [ ] And I try to add a new card
- [ ] Then I will see the stripe website where I can add my card info in the form
- [ ] When I finish submitting the form
- [ ] Then I will see the newly created card as selected in the CardSelector

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Remove android install permission from the play store build



## Goal

We need to remove the REQUEST_INSTALL_PACKAGES permission for the play store build in order to avoid complaints.


## What needs to be done

Remove the permission only for the play store build. We still need the permission for the full android version (used in the auto-update)

## QA

-


## UX/Design

-


## Acceptance Criteria

- [ ] Play store builds should not have the REQUEST_INSTALL_PACKAGES permission in the manifest
- [ ] Common android builds should have the REQUEST_INSTALL_PACKAGES permission in the manifest

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Hide Chat icon behind feature flag

<!---
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

Hide chat icon behind feature flag until the app is ready in google store. 


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Add a feature flag and hide the icon in the header. 

## 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.
--->


## Personas

<!---
Who does this user impact and why (optional)
--->
Developers 

## 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
--->

- [ ] the chat icon is hidden in all header instances. 

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Push notifications not working on RC



### Summary

The push notification package is not returning the device token. 
It may be caused by the RN update.

### Steps to reproduce

- Check push

### Platform information 

Android

### What is the current *bug* behavior?

The push notification token is not sent to the JS side

### What is the expected *correct* behavior?

The token event should be fired

### Relevant logs and/or screenshots

-

### Possible fixes

-

Story points: 3.0