Fixed touch tracking in the range slider

[grzesiek2010]

Closes #6607

Why is this the best possible solution? Were any other approaches considered?

The way we tracked touch events was incorrect. We set a listener and in that listener tried to call v.onTouchEvent(event) where v refers to the view that received the touch event. So it was like overriding the listener but also trying to call the default implementation and the order of those calls caused the problems with setting/reading values.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

We need to test setting values in the range widgets (only those that use sliders, there is no need to test the picker one). Nothing else should be affected.

Do we need any specific form for testing your changes? If so, please attach one.

No.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
• added a comment above any new strings describing it for translators
• added any new strings with date formatting to DateFormatsTest
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines

[dbemke]

Tested with Success!

Verified on a device with Android 10

Verified cases:

• issue Number slider does not work as expected in the form with field list. #6607 doesn't occur
• regression checks in range widget
• different range widgets on a field-list
• don't keep activities enabled/disabled

[WKobus]

Tested with Success!

Verified on a device with Android 15