[Android] Fix News scroll issue

[tapanmodh]

Resolves brave/brave-browser#21475

Submitter Checklist:

• I confirm that no security/privacy review is needed, or that I have requested one
• There is a ticket for my issue
• Used Github auto-closing keywords in the PR description above
• Wrote a good PR/commit description
• Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
• Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
• Checked the PR locally: npm run test -- brave_browser_tests, npm run test -- brave_unit_tests, npm run lint, npm run gn_check, npm run tslint
• Ran git rebase master (if needed)

Reviewer Checklist:

• A security review is not needed, or a link to one is included in the PR description
• New files have MPL-2.0 license header
• Adequate test coverage exists to prevent regressions
• Major classes, functions and non-trivial code blocks are well-commented
• Changes in component dependencies are properly reflected in gn
• Code follows the style guide
• Test plan is specified in PR before merging

After-merge Checklist:

• The associated issue milestone is set to the smallest version that the
  changes has landed on
• All relevant documentation has been updated, for instance:
  • https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
  • https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
  • https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
  • https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
  • https://github.com/brave/brave-browser/wiki/Custom-Headers
  • https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
  • https://github.com/brave/brave-browser/wiki/QA-Guide
  • https://github.com/brave/brave-browser/wiki/P3A

Test Plan:

[samartnik]

lgtm

[alexsafe]

@tapanmodh we can probably get rid of the ScrollView import too. and replace it in calls like mParentScrollView.fullScroll(ScrollView.FOCUS_UP); i think those are the only references left

[kjozwiak]

Verification PASSED on Pixel 6 running Android 12 using the following build(s):

1.39.73 Chromium: 101.0.4951.34

• verified the STR/Cases outlined via Brave News - "velocity" (when scrolling up) stops when top is reached brave-browser#21475 (comment)
• ensured that scrolling up all the way back to the widgets worked without any issues (scrolling velocity wasn't stopped)
• ensured that scrolling down from the start of the feed worked without an issues (scrolling velocity wasn't stopped)
  • as mentioned below, news scroll velocity stops when scrolling down at the start of the feed - follow up to #21475 brave-browser#22434 was created as a follow up
• ensured that scrolling through the news feed is a smooth experience and users don't run into any issues
  • other than news scroll velocity stops when scrolling down at the start of the feed - follow up to #21475 brave-browser#22434, ensuring there's no other dead spots
  • ensuring that it doesn't appear janky/laggy and is responsive when swiping either up or down
  • ensured that swiping starts scrolling through the feed and eventually the velocity slows down/comes to a stop

Created brave/brave-browser#22434 as a follow up. The scrolling has definitely improved but we're still running into one case where the velocity of the scroll basically stops when it hits a certain area of the feed. This usually happens at the start of the feed.