fix: wrong pointerInput invoked on scroll inside message list [WPB-3525]

[trOnk12]

---

PR Submission Checklist for internal contributors

• The PR Title

  • conforms to the style of semantic commits messages¹ supported in Wire's Github Workflow²
  • contains a reference JIRA issue number like SQPIT-764
  • answers the question: If merged, this PR will: ... ³

• The PR Description

  • is free of optional paragraphs and you have filled the relevant parts to the best of your ability

---

What's new in this PR?

Issues

• When scrolling up in the conversation list and back to bottom, the click and onlong click lambda did not get updated, causing the lambda to invoke functions with misplaced data.

Solutions

• Update pointerInput with each change of text layout.

Dependencies (Optional)

If there are some other pull requests related to this one (e.g. new releases of frameworks), specify them here.

Needs releases with:

• GitHub link to other pull request

Testing

Test Coverage (Optional)

• I have added automated test to this contribution

How to Test

Briefly describe how this change was tested and if applicable the exact steps taken to verify that it works as expected.

Notes (Optional)

Specify here any other facts that you think are important for this issue.

Attachments (Optional)

Attachments like images, videos, etc. (drag and drop in the text box)

---

PR Post Submission Checklist for internal contributors (Optional)

• Wire's Github Workflow has automatically linked the PR to a JIRA issue

---

PR Post Merge Checklist for internal contributors

• If any soft of configuration variable was introduced by this PR, it has been added to the relevant documents and the CI jobs have been updated.

---

References

1. https://sparkbox.com/foundry/semantic_commit_messages
2. https://github.com/wireapp/.github#usage
3. E.g. feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764.

[CLAassistant]

All committers have signed the CLA.

[github-actions]

@trOnk12 looks like you are rolling back kalium to a previous commitish.

This means that the PR's target branch (release/candidate) is using a newer version of Kalium, and the changes in this PR will rollback Kalium to an older version.

release/candidate	This PR
d42a5fd2275d8f23be3b7d0bff9335ff4c87edfc	67514c7ec1394fbb477c9c3fb92600838f2642a5

Is this intentional?

[github-actions]

Test Results

511 tests   510 ✔️  22s ⏱️
  74 suites      1 💤
  74 files        0 ❌

Results for commit 40953a0.

[github-actions]

APKs built during tests are available here. Scroll down to Artifacts!

[AndroidBob]

Build 749 succeeded.

The build produced the following APK's:

• com.wire.android-v4.3.0(7157761)(7157761)-staging-compat.apk