[py] Allow overriding the default 250 msecs duration of pointer movement

[space88man]

Description

Set the duration of a pointer movement by adding
a kwarg duration= to ActionChains constructor that will percolate down to PointerInput.create_pointer_move
via ActionBuilder and PointerActions. Addresses #7281.

Motivation and Context

There is a default duration of 250 msecs (DEFAULT_MOVE_DURATION) set in PointerInput. However
PointerActions, a consumer of the method PointerInput.create_pointer_move, does not override this duration.
Thus every pointer move incurs 250 msecs.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[CLAassistant]

All committers have signed the CLA.

[space88man]

More context; users of PointerInput have to maintain their own code fork with DEFAULT_MOVE_DURATION = 0 in pointer_input.py or monkey patch

# the current workaround
# monkey patching for DEFAULT_MOVE_DURATION = 250
# the default duration for a pointer move is 250 msecs
# this is not overridden by pointer_actions.py
# to shorten the duration we have to monkey patch the method
orig_mthd = PointerInput.create_pointer_move

def new_mthd(self, duration=0, x=None, y=None, origin=None):
    orig_mthd(self, duration=duration, x=x, y=y, origin=origin)

PointerInput.create_pointer_move = new_mthd

[AutomatedTester]

thanks for the patch!

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information