[HOLD for payment 2023-11-02] Implement bidirectional pagination in ReportActionsList

[roryabraham]

HOLD on:

• [HOLD for payment 2024-01-18] Fix FlatList jumping #23220
• [HOLD for payment 2023-08-17] [$1000] Create Onyx migration for previousReportActionID #23221

Part of the Comment Linking project

Main issue: #20282
Doc section: https://docs.google.com/document/d/1v-ZaIRTZL5LIsyPWB0IopBNNgCajf5WC1OA8cVKtd8I/edit#bookmark=id.tgiglcuu8pr9
Project: Comment Linking

For bidirectional scrolling, we need to enable the addition of new data to the chat from both ends. The top end utilizes built-in methods onEndReachedThreshold and onEndReached. We need to start using onStartReached for the bottom end as well.

We should call the GetOlderActions API onEndReached and GetNewerActions API onStartReached.

Also, this PR should enable the CheckForPreviousReportActionID migration being built here.

Manual Test Steps

TBD

Automated Tests

TBD

Issue Owner

Current Issue Owner: @sonialiap

[melvin-bot]

Triggered auto assignment to @sonialiap (NewFeature), see https://stackoverflowteams.com/c/expensify/questions/14418#:~:text=BugZero%20process%20steps%20for%20feature%20requests for more details.

[roryabraham]

cc @perunt

[melvin-bot]

Triggered auto assignment to Design team member for new feature review - @shawnborton (NewFeature)

[perunt]

Here we go! 🚀

[melvin-bot]

This issue has not been updated in over 15 days. @perunt eroding to Monthly issue.

P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do!

[melvin-bot]

@perunt Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[melvin-bot]

@perunt 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

[melvin-bot]

@perunt 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

[melvin-bot]

@perunt 10 days overdue. Is anyone even seeing these? Hello?

[melvin-bot]

⚠️ Looks like this issue was linked to a Deploy Blocker here

If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.

If a regression has occurred and you are the assigned CM follow the instructions here.

If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.91-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Bidirectional pagination #26166

If no regressions arise, payment will be issued on 2023-11-02. 🎊

After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.

• External issue reporter
• Contributor that fixed the issue
• Contributor+ that helped on the issue and/or PR

For reference, here are some details about the assignees on this issue:

• @perunt does not require payment (Contractor)

[melvin-bot]

BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

• [@perunt] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
• [] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.

[melvin-bot]

@perunt Eep! 4 days overdue now. Issues have feelings too...

[roryabraham]

Assigning new feature and @s77rt for C+ payment

[roryabraham]

@sonialiap can you please issue C+ review payment to @s77rt then close this out?

[sonialiap]

@s77rt offer sent

[webmaster1022]

Hi, How are you?
May I work with this issue?
Thanks!

[melvin-bot]

📣 @webmaster1022! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[sonialiap]

@webmaster1022 this issue has been resolved. Please check out the Open issues with the Help Wanted label for issues available to be worked on.

[s77rt]

@sonialiap Accepted! Please make sure the payment is $125 (for two regressions: #30423 and #30729). Thanks!

[sonialiap]

Thanks @s77rt , payment of $125 sent ✔️