giseldo/neodataset huggingface dataset:
Boosts don't seem to load beyond 15

<!---
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

I was trying to look at some of my older boosts today, but they didn't load beyond first 15.

### Steps to reproduce

1. Have a LOT of boosts in boost console (more than 15)
2. Try scrollig to the oldest boost
3. See that more than 15 won't load

### Platform information 

iOS

### What is the current *bug* behavior?

I can't see more than 15 boosts in console

### What is the expected *correct* behavior?

I should be able to see more than 15 boosts in console

### 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: 3.0
Update Boost Settings UI to introduce new setting options

<!---
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 value to Minds+ subscription prop
- Give Minds+ customers more control of their content
- Give content owners more control over how their content is presented
- Enable eligible customers to earn more from Boost partners by enabling more lucrative audience targeting

## What needs to be done

Enable Minds+/Pro subscribers to disable Boosts on their content, including channel pages, SEPs, etc.

Bonus if the control is exposed to non-subscribers and used as a point of converting to a Minds+ subscriber.

Give all users an option to enable/disable Controversial Boosts from appearing on pages they own (channel pages, SEPs, etc.).

https://gitlab.com/minds/engine/-/issues/2519

## 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.
--->

See https://gitlab.com/minds/minds/-/issues/3699

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] Is Mobile Required?

## 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.
--->
Boost partner epic

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] UI implemented adhering to designs on https://gitlab.com/minds/minds/-/issues/3699
- [ ] Implement new configuration column value for boost serving
- [ ] Settings page should call a new endpoint that returns specific boost settings

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Add a share icon to comments

<!---
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 comments to copied and shared

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Add a share icon to comments. Place this icon next to thumbs and re-use the same share modal we use for activity posts.

## 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.
--->

[Figma](https://www.figma.com/file/QJiT80vS4yOyprLiafWfbM/Comments?node-id=2%3A1161&t=fQFpi0K33JaNUXTz-1)

**Web**

![Post_Entity](/uploads/2c9e23e0756cdfaf7c4c577b79ebe400/Post_Entity.png)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] Is Mobile Required?
## 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
--->

- [ ] Add share icon and modal to all comments
- [ ] Update the share modal to say "Share this comment" instead of "Share this post"

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Promoting a patch release to store release

<!---
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

We want to be able to release a patch version to store using tags

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

- include the build stage in both patch and nonpatch tags but make it manual on patch versions.

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

N/A

## 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)
--->

N/A

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

N/A

## 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
Create Cash account not navigating to Stripe connect

<!---
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

Create Cash Account button in superminds console (if you haven't connected a cash account yet) doesn't navigate the user to stripe connect 

### Steps to reproduce

- have a user that doesn't have a cash account
- navigate to superminds console
- tap on create cash account
- notice nothing happens

### Platform information 

all

### What is the current *bug* behavior?

navigation doesn't happen

### What is the expected *correct* behavior?

nav should happen

### Relevant logs and/or screenshots

N/A

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Registration crashes due to old react-native-modal library

<!---
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

Registration crashes due to old react-native-modal library

### Steps to reproduce

Try to create a new user from a logged-in flow, the screen will crash after registration is complete

- not tested on android
- not tested from logged out flow

### Platform information

tested on iOS, but should be all

### App version

latest

### What is the current *bug* behavior?

crash

### What is the expected *correct* behavior?

crash is bad

### Relevant logs and/or screenshots

N/A

### Possible fixes

update lib

Story points: 2.0
HotFix - Hide 'Verify account' in the Drawer

<!---
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

Remove any reference of the in-app verification if FF disabled.
<!---
Clearly outline the goal of the issue and why we are doing it
--->


## What needs to be done

Hide the 'Verify account' line item in Drawer
<!---
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
--->
Check if 'Verify account' is no more in Drawer.


## UX/Design

<!---
Sufficient wireframes have been presented and understood by the development team. Full mockups are not required and re-usable components are encouraged.
--->

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [ ] Is Mobile Required?

## 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.
--->

[Merge Request](https://gitlab.com/minds/mobile-native/-/merge_requests/2125) 

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] The 'Verify account' item is not present in Drawer

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Boost console on mobile shows tokens instead of cash

<!---
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

![image](/uploads/a3ccdbab32c74bd0407882520ff66ca6/image.png)

### Steps to reproduce

1. Do a cash boost
2. Look at the boost console on mobile
3. See it says tokens, not cash

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

Cash shows as tokens

### What is the expected *correct* behavior?

Cash should show as cash

### 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
Fix bug regarding undefined in getAvatarSource

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

undefinded calling getAvatarSource

### What is the expected *correct* behavior?

not to be undefined or not to call getAvatarSource

(What you should see instead)

### 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: 3.0
Changelog parser breaking the pipeline

<!---
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

(Summarize the bug encountered concisely)

### Steps to reproduce

(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)

### What is the current *bug* behavior?

(What actually happens)

### What is the expected *correct* behavior?

(What you should see instead)

### 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
Summary screen doesn't show estimated reach on mobile

<!---
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

Summary screen doesn't show estimated reach on mobile

### Steps to reproduce

1. make boost
2. go to summary screen
3. see the that it's unknown

(works fine on desktop)

### Platform information 

ios, android

### What is the current *bug* behavior?

Reach shown as unknown on summary screen

### What is the expected *correct* behavior?

Reach should be shown as is shown on desktop

### 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
Enable Google Pay on Web/Mobile Web

<!---
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
--->

Accept Google Pay for whichever products possible


## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

- Boost
- Plus
- Pro
- Other?
- https://support.google.com/googlepay/answer/7644068?hl=en
- https://stripe.com/docs/google-pay?platform=react-native
- https://pay.google.com/about/business/
- Investigate how to allow Google Pay to work on android.


## 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
Discovery boost feed not working with v3 boosts



### Summary

The boosts feed is empty on discovery (Boost v3)

### Steps to reproduce

Check discovery tab

### Platform information 

both

### What is the current *bug* behavior?

Feed empty

### What is the expected *correct* behavior?

it should show v3 boosts

### Relevant logs and/or screenshots

-

### Possible fixes

TBD

Story points: 2.0
v3 boosts are not being injected in the feed



### Summary

No boosts on the feed

### Steps to reproduce

Check the feed

### Platform information 

both

### What is the current *bug* behavior?

v3 boosts are not injected into the feed

### What is the expected *correct* behavior?

They should be injected

### Relevant logs and/or screenshots

-

### Possible fixes
TBD

Story points: 2.0
Stripe's "Know Your Customer" Identity Verification Page Not Appearing

<!---
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
When attempting to complete the wallet / cash (Stripe's "know your customer" identity) verification process, the corresponding stripe.com based page fails to appear. 

### Steps to reproduce
View the wallet / cash /settings section and then attempt to complete the Stripe based "know your customer" identity verification process.

### Platform information 

Tested using Android mobile client application (version 4.31.5).

### Relevant logs and/or screenshots
![stripe-kyc-identity-verification-page-not-appearing_issue_mobile-native_4768](/uploads/8fb8d51de40625419415e3332030b47e/stripe-kyc-identity-verification-page-not-appearing_issue_mobile-native_4768.mp4)<br>
<i>Wallet / cash / settings -  "know your customer" identity verification / bank account information process as seen via the Android mobile client application.</i>

Story points: 3.0
Add a share icon to comments

<!---
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 comments to copied and shared

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->
Add a share icon to comments. Place this icon next to thumbs and re-use the same share modal we use for activity posts.

## 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.
--->

[Figma](https://www.figma.com/file/QJiT80vS4yOyprLiafWfbM/Comments?node-id=2%3A1161&t=fQFpi0K33JaNUXTz-1)

**Web**

![Post_Entity](/uploads/f7279fa4b4cd9f98c62c952f0670fafe/Post_Entity.png)

## Mobile

<!---
Does a mobile card need to be created? Any notes for mobile?
--->

- [x] Is Mobile Required?
## 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
--->

- [x] Add share icon and modal to all comments
- [ ] Update the share modal to say "Share this comment" instead of "Share this post"

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Holding rewards show as zero in wallet

<!---
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

Holding rewards show as zero in wallet

![image](/uploads/7e1e6df9d5c4b90f349dbe4e798c6995/image.png)

### Steps to reproduce

1. Have some on-chain tokens
1. Look into your wallet

### Platform information 

Brave, Win10

### What is the current *bug* behavior?

Wallet shows zero in holding section

### What is the expected *correct* behavior?

Wallet should show proper amount in holding section

### 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)

### UX Design

[Figma](https://www.figma.com/file/tBOvE8yIILW49vECySCLpZ/Earnings?node-id=163%3A2911&t=lKTi6szGDxu4oxNk-1)

**Web**

![Holdings_Web](/uploads/ae1a76a1339473379a5f416e5f4436c8/Holdings_Web.png)

**Mobile**

![Holdings_Mobile](/uploads/44a482dcc5934f0eb771201599fc4b4b/Holdings_Mobile.png)

Story points: 2.0
V3 boosts are not injected into the feed



### Summary

The new v3 boosts are not injected in the feed

### Steps to reproduce

check boosts

### Platform information 

both

### What is the current *bug* behavior?

It is not showing the v3 boosts (Showing v2)

### What is the expected *correct* behavior?

It should be using the new endpoint

### Relevant logs and/or screenshots

-

### Possible fixes

The FF is checked too soon that is why it is always false

Story points: 2.0
Invite friend in-feed notice should be dismissible



## Goal

The in-feed notice should be dismissible

![imagen](/uploads/29cc7a75ad0fbd716189dbe16c89726a/imagen.png)

## What needs to be done

Add a dismiss option

## QA

Check that is dismissible


## UX/Design

-

## Experiments
-


## Acceptance Criteria

- [ ] User should be able to dismiss the notice

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Fix notification text descriptions

<!---
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

(Summarize the bug encountered concisely)
the texts in notifications are wrong.

### Steps to reproduce

go in notification screen
(How one can reproduce the issue - this is very important)

### Platform information 

(Browser, device, system stats, screen size)
All

### What is the current *bug* behavior?
- the texts in notifications are wrong.
(What actually happens)

### What is the expected *correct* behavior?
- the texts in notifications should be right.

(What you should see instead)

### Relevant logs and/or screenshots
![image](/uploads/cdbfc3e4d8bef9a3a973b1c79c53b1de/image.png)

(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: 3.0