giseldo/neodataset huggingface dataset:
Add visual confirmation on code-push update

<!---
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

Check for code-push updates and add a visual confirmation in a bottom sheet to download, install and restart the app.

## What needs to be done

- automatically download any updates from the prod channel
- add a code-push check for updates on focus in home screen
- show a banner between the moments and the last posts popping up a confirmation bottom-sheet with text to download an update
- install and restart the app on confirmation

## QA

N/A

## UX/Design

Need to get the confirmation text.

## Acceptance Criteria
1. 
- GIVEN that I go to home screen
- AND the code-push check for updates returns true
- THEN I see a top banner with install now message
2.
- GIVEN that I see the code-push top banner confirmation
- WHEN I press on install now
- THEN the code-push update will be downloaded and installed 
- AND the app will restart
3.
~~- GIVEN that I see the code-push bottom-sheet confirmation~~

~~- WHEN I press on NO button~~

~~- THEN the top widget confirmation popup will hide~~

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 3.0
Add staging code-push support in DevTools screen

<!---
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 toggle in developer menu to switch between production and staging code-push keys. Both keys pairs will be provided in the env file.

## What needs to be done

- Add toggle component in developer menu to change code-push channel
- On toggle to staging channel, download, install and restart the app if any present code-push

## QA

No need a new build for iOS and Android to test the channel switch.

## UX/Design

Add new item in the DevTools screen with either a toggle switch component or a check to mark the staging channel selection.

## Acceptance Criteria

- GIVEN that I'm in the DevTools screen
- WHEN I press on the line item with the staging code-push
- THEN the app will download and install the update
- AND the app will restart
- AND the changes will be present in the app

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design

Story points: 5.0
Two avatars show in the stories top bar

<!---
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

For certain users, two avatars appear in the story top bar. In the light of adding a new avatar in the header, we'll end up with three.

### Steps to reproduce

On homescreen for user valinaga.

### Platform information 

Both

### What is the current *bug* behavior?

GIVEN that I'm in the home screen
WHEN I look at the stories top bar
THEN I see 2 avatars present, one for New moments, and one showing my username.

### What is the expected *correct* behavior?

GIVEN that I'm in the home screen
WHEN I look at the stories top bar
THEN I should see the New moments with a camera icon (or similar)
AND I should not see my avatar with my username.

### Relevant logs and/or screenshots

![image](/uploads/cb4dd94efa953ada185b5fadf4fe0920/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Notifications tab filtering is not working correctly

<!---
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

As a user I want to see the notifications filtered based on the top tab buttons.

### Steps to reproduce

GIVEN that I'm in the Notifications screen
WHEN I tap on on Tags/Comments/Subscribers/Votes/Reminders 
THEN the filtered content appears for a sec 
AND then all content is rendered

### Platform information 

Both

### What is the current *bug* behavior?

GIVEN that I'm in the Notifications screen
WHEN I tap on on Tags/Comments/Subscribers/Votes/Reminders 
THEN the filtered content appears for a sec 
AND then all content is rendered

### What is the expected *correct* behavior?

GIVEN that I'm in the Notifications screen
WHEN I tap on on Tags/Comments/Subscribers/Votes/Reminders 
THEN the filtered content should be displayed and preserved

### Relevant logs and/or screenshots

![Simulator_Screen_Recording_-_iPhone_13_-_2022-10-21_at_15.29.05](/uploads/ae47e9013f5df3921ba6b7a96e2410b0/Simulator_Screen_Recording_-_iPhone_13_-_2022-10-21_at_15.29.05.mp4)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Console should show pending/accepted Supermind offers first in the console and then sort by date (app)

<!---
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

The console currently shows all the offers only sorted by date. 
- For **inbound** Superminds, we should place the **pending** offers on the top sorted by date, and then sort the rest of the offers also by date.
- For **outbound** Superminds, we should place the **accepted** offers on the top sorted by date, and then sort the rest of the offers also by date.


## 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.
--->


## 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
--->

- [ ] Change Supermind console default filter > Inbound tab to `Pending`.

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 1.0
Change text of wire received email setting

<!---
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've updated the behavior of the wire_received notif to also control Superminds, this needs reflecting on clients.

## What needs to be done

We need to reflect this on the mobile client - see acceptance criteria.

## QA

Check setting label

## UX/Design

N/A

## Personas

Users who want to change their email settings for Supermind

## Experiments

N/A

## Acceptance Criteria

- Copy text from here to change the text for the wire received email setting on mobile https://gitlab.com/minds/front/-/merge_requests/2085

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [x] Weighted
- [x] QA
- [ ] UX/Design
- [x] Personas
- [x] Experiments

Story points: 1.0
In-feed notice for pending Supermind offers (app)

## Goal

Increase the acceptance rate for Supermind offers.

## What needs to be done

Implement a new in-feed notice that prompts a user with pending Supermind offers to act on those offers.

| Notice                    | Description                                                                   | Dismissable | Position | Sticky | Display priority | Conditions                          | Primary action                                   | Secondary action |
|---------------------------|-------------------------------------------------------------------------------|-------------|----------|--------|------------------|-------------------------------------|--------------------------------------------------|------------------|
| You have Supermind offers | Reply to your fans to claim cash or tokens before your pending offers expire. | No          | Top      | No     | 1.1              | User has pending Supermind offer(s) | Let's go (clicks to Supermind console > Inbound) | n/a              |

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->


## UX/Design

n/a

## Personas

Creators

## Experiments

n/a

## Acceptance Criteria

- [ ] Given a user has pending Supermind offers, and they've already confirmed their email address, when they visit the Newsfeed, then an in-feed notice informs them of their pending offers.
- [ ] The in-feed notice displays the total value of their pending Supermind offers.
- [ ] Clicking the `Let's go` button directs the user to the Supermind console > Inbound tab.
- [ ] Track click events on Snowflake

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 5.0
Superminds replies and reminds are not throwing the correct toaster message

### Summary

Supermind replies and remind toasters say supermind request has been sent successfully. The toaster message should be updated when reminding or replying to a supermind post. 

### Steps to reproduce

1. Open minds app.
2. Send a supermind post to a user.
3. Login with other use and reply to that supermind post. 
4. Reply/Remind a supermind post. 

### Platform information 

All platforms - 4.29.1 RC

### What is the current *bug* behavior?

After replying or reminding a supermind post, the toaster message does not say you replied or reminded. Instead says that your supermind request was sent. 

### What is the expected *correct* behavior?

Supermind toaster message should be correct. 

### Relevant logs and/or screenshots

![image](/uploads/61983f8523330e474320e1f17094d210/image.png)
![image](/uploads/227d125180d77e04c1da37f7a701bcb4/image.png)

Story points: 1.0
Opening Superminds offer from email throws an error

### Summary

Deep links from super minds emails are not working. 
Found by Bill. 

### Steps to reproduce

1. Open minds email for superminds offer.
2. Takes you to minds app. 
3. Press continue on superminds onboarding page. 
4. On superminds page, an error is throw. 

### Platform information 

Android

### What is the current *bug* behavior?

Throws "Error. Try Again"

### What is the expected *correct* behavior?

Should open the supermind offer

### Relevant logs and/or screenshots

![image](/uploads/6dfbb41c99bb28385aa578d2a801670e/image.png)

Story points: 3.0
Deprecate ZoomView in favor of ImageGallery

<!---
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
--->

The ZoomView can be deprecated in favor of ImageGallery. This brings in the engagement buttons and provides for a more consistent experience

## What needs to be done

<!---
Clearly detail what needs to be done to achieve the goal set out above
--->

deprecate ZoomView and use ImageGallery for all images. Remove double-tap as well. A single tap on any image should open the gallery view

## QA

<!---
Consideration is given to how the issue will be demoed and tested prior to being deployed
--->

Make sure AC are implemented

## 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)
--->

All

## Experiments

<!---
Experiments are not required, but it should be made clear if one is expected. If experiments are required, the hypothesis should be outlined.
--->

Not required

## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

- [ ] TBD

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design
- [ ] Personas
- [ ] Experiments

Story points: 2.0
Pull down to dismiss an image from gallery view

<!---
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

When opening the image on app into the gallery view, the only way to dismiss it is by pressing x. It should also be possible to pull down to dismiss that image, the way it's possible to dismiss an image that is zoomed in


## 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.
--->


## 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: 3.0
Remove top space in Supermind onboarding on android

<!---
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 

Android

### What is the current *bug* behavior?

There is a top space above the title.

### What is the expected *correct* behavior?

No space above the title.

### Relevant logs and/or screenshots

### Possible fixes

Change marginTop from 125 to conditional 125 for iOS and 70 for android.

MR: https://gitlab.com/minds/mobile-native/-/merge_requests/1948

Story points: 1.0
Engagement Rewards Activity Multiplier Tooltip Typographical Error Within Mobile Application

<!---
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 relation to https://gitlab.com/minds/front/-/issues/4701, the hardcore section within the engagement rewards activity multiplier tooltip still displays "Activity six days over the past six days". This should display "Activity six days over the past seven days".

### Relevant logs and/or screenshots
![engagement-rewards-activity-multiplier-tooltip-typographical-error_issue_front_4701](/uploads/b0e2406b373f6397db6e3b22547d77ce/engagement-rewards-activity-multiplier-tooltip-typographical-error_issue_front_4701.png)<br>
<i>Engagement activity multiplier tooltip.</i>

Story points: 1.0
Boost console: Activity posts do not appear for rejected Boosts

<!---
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 Boost console shows a history of Boosts and their status.

Completed Boosts show the activity post that was boosted.

However, Boosts that are rejected/cancelled do not show the activity post.

### Steps to reproduce

- Make a Boost
- Get rejected (e.g. due to backlog overflow)
- View the Boost console

### Platform information 

App

### App version

for a few versions

### What is the current *bug* behavior?

- Activity posts do not appear for rejected Boosts

### What is the expected *correct* behavior?

- Activity posts appear for all Boosts, regardless of status

### Relevant logs and/or screenshots

![image](/uploads/794f43d318655cea32c6ccc3785214b4/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 2.0
Implement new mobile MFE folder architecture

<!---
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 new mobile MFE folder architecture with stand-alone modules.

## What needs to be done

Create new folder architecture and port Analytics module as an example.

## QA

Regression tests required.

## UX/Design

N/A.

## Acceptance Criteria

- [ ] All analytics functionalities must be present.

## Definition of Ready Checklist

- [x] Definition Of Done (DoD)
- [x] Acceptance criteria
- [ ] Weighted
- [x] QA

Story points: 5.0
[mobile] Supermind creator onboarding shows incorrect platform fee

<!---
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 platform fee indicated on the Supermind creator onboarding indicates platform fee is 10%. This is incorrect -- the platform fee is 15%.

### Steps to reproduce

- Launch the Supermind console for the first time
- The Supermind creator onboarding appears

### Platform information 

- Mobile app, iPhone, iOS 16

### What is the current *bug* behavior?

The message indicates the platform fee is 10%.

### What is the expected *correct* behavior?

The message indicates the platform fee is 15%.

### Relevant logs and/or screenshots

![image](/uploads/4ccf41e3693e8bfdb1360b0a031cfbdf/image.png)

### Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Story points: 1.0
Supermind outbox pagination not working correctly

<!---
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

Supermind outbox appears to stop at 12 entries implying a possible pagination issue. May also apply to inbox.

### Steps to reproduce

1. Have more than 12 entries in your outbox
2. Scroll down

### Platform information 

Mobile, reported on iOS

### What is the current *bug* behavior?

Can't load more than 12

### What is the expected *correct* behavior?

Should paginate

### 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
Add avatar to the home feed header

<!---
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

Make it easy to get to your own profile by moving the avatar on the header.

## What needs to be done

Add the avatar in the home header.

## QA

Normal testing

## UX/Design

Ideally it would be helpful a design to accommodate logo/icon with avatar in the header.
https://www.figma.com/file/nzsefF70ixE0nGAuIShnFG/Revised-Mobile-Header?node-id=0%3A1


## Acceptance Criteria

<!--
Everyone should be able to understand what is expected to be delivered
--->

GIVEN that I'm on the home screen
WHEN I press on my avatar
THEN I navigate to my profile

GIVEN that I'm on the home screen
WHEN I scroll down a lot
AND scroll up once
THEN I should see the avatar on the header
AND I should be able to click on it

## Definition of Ready Checklist

- [ ] Definition Of Done (DoD)
- [ ] Acceptance criteria
- [ ] Weighted
- [ ] QA
- [ ] UX/Design

Story points: 3.0
On session selector (account selector), the names show wrong

<!---
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 got a bug, where my accounts get renamed to my main account, and appear as it's that account:
- The first bashynx is supposed to be bashynx
- Second bashynx should be my admin account bashyadmin
- Third bashynx should be bashytest01

![image](/uploads/0d862a20d9e5451a30d27798610cbc40/image.png)

### Steps to reproduce

Seems to happen after clicking on notification for account other than my main (bashynx)

Restarting app didn't help - I have reinstalled it, and that naturally fixed it, as I had to add new accounts. I am monitoring it if it will happen again.

### Platform information

iPhone XR

### App version

Current (4.29 I believe)

### 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: 5.0