Select tuplet when calling next-element prev-element actions

[efu98]

Resolves: #17600

Select tuplet when calling action next-element and prev-element

• I signed the CLA
• The title of the PR describes the problem it addresses
• Each commit's message describes its purpose and effects, and references the issue it resolves
• If changes are extensive, there is a sequence of easily reviewable commits
• The code in the PR follows the coding rules
• There are no unnecessary changes
• The code compiles and runs on my machine, preferably after each commit individually
• I created a unit test or vtest to verify the changes I made (if applicable)

[shoogle]

Thanks for this! You've nearly solved the next-element function (but not quite), and you also need to do the same in the other direction with previous-element (Alt+Left).

From #17600 (comment):

If you go in the other direction with Alt+Left then the elements should be selected in reverse order.

[Jojo-Schmitz]

Going back does not select them in reverse order, both directions select the tuplet first.
May not be a great deal, at least it does get selected both ways and sort of it is the last and first element at the same time in a way.

[shoogle]

@Jojo-Schmitz is right, when going backwards it's not in reverse order.

Here's what we want to see:

Forwards (Alt+Right)	Backwards (Alt+Left)
1. D 2. Tuplet 3. E 4. F 5. G 6. A	6. A 5. G 4. F 3. E 2. Tuplet 1. D

[efu98]

Hii! Sorry for taking so much time making the changes, PR is ready to be reviewed now!

[efu98]

(Sorry, i was trying to remove the change request)

[shoogle]

Functionality is there, thanks! Just a couple of comments about the code.

[efu98]

Hello! Thank you for the review ! I have edited the code according to the comments

[shoogle]

Thanks! Please fix the build and then squash all your commits into one.

[shoogle]

Great job, thanks!