perf(input): passive event listener for touch start events

[sean-perkins]

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Some docs updates need to be made in the ionic-docs repo, in a separate PR. See the contributing guide for details.
• Build (npm run build) was run locally and any changes were pushed
• Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

When using an input with scroll assist or an input with a clear action, there is violations that are logged in the dev console:

[Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event.
Consider marking event handler as 'passive' to make the page more responsive.

Issue URL: #25599

What is the new behavior?

• Refactors Input to use onPointerDown instead of onTouchStart (confirmed this does not regress the existing bug associated with using onTouchStart: 4.1.1 - clearInput doesn't clear when circle is clicked #15319)
• Registers passive event listeners in the scroll assist util for touchstart

Does this introduce a breaking change?

• Yes
• No

Other information

Dev-build: 6.1.14-dev.11657566839.18ed2481 ✅

Since the bug associated with this PR does not have functional problems, it is difficult to know the affected changes, if any. I confirmed that the clear action continues to work in browser and on device. I also confirmed the scroll assist does not appear to have regressed. The originally reporter also confirmed the dev-build.

[liamdebeasi]

Could also consider this a perf instead of a fix since it should help with scrolling performance in some cases

[sean-perkins]

@liamdebeasi I like the idea of targeting at perf since there isn't broken/buggy behavior reported 👍