CATROID-1106: GlideToPositionBrick

[rinaschedl]

https://catrobat.atlassian.net/browse/CATROID-1106

A new Brick (Feature) is created.
Brick Behavior:
The Brick has 3 options:
-random position
- the sprite glides to a random position
-touch position
- the player has to touch a position where the sprite then goes
-other sprite position
- the sprite glides (and at the moment follows) a other sprite till the other sprite stops.
- this part is not finally discussed: may we change it so that the sprite goes to the startposition from the other sprite and don't follow at all.

Program changes:
create 3 Actions and 3 Actionstest, GlideToPositionBrick, brick_glide_to_position
changes in BrickValue, ActionFactory

Commitlist during coding:
TestGlideToRandomPositionDestination Test; flact:red
TestGlideToRandomPositionDestination flact:green; createGlidetoRandomPositionAction;
Refactoring and knew Test: GlideBehavior, bove Tests are green
show Brick in Bricklist with the correct attributs. Attributes don't work yet.
changed all glide_to_.... to glide_to_position_... so to better distinguish between.
last commit before PairProgramming Session with Thomas
glideToTouchPosition ready, brick test by hand and the tests are grenn
refactor the ActionTest: canceled all deprecated lines; correct misspellings;
add GlideToOtherSpritePosition
refactor GlideToRandomPositionAction.kt
Refactoring all files that changed in the ticket Catroid-1106

Your checklist for this pull request

Please review the contributing guidelines and wiki pages of this repository.

• Include the name of the Jira ticket in the PR’s title
• Include a summary of the changes plus the relevant context
• Choose the proper base branch (develop)
• Confirm that the changes follow the project’s coding guidelines
• Verify that the changes generate no compiler or linter warnings
• Perform a self-review of the changes
• Verify to commit no other files than the intentionally changed ones
• Include reasonable and readable tests verifying the added or changed behavior
• Confirm that new and existing unit tests pass locally
• Check that the commits’ message style matches the project’s guideline
• Stick to the project’s gitflow workflow
• Verify that your changes do not have any conflicts with the base branch
• After the PR, verify that all CI checks have passed
• Post a message in the catroid-stage or catroid-ide Slack channel and ask for a code reviewer

[github-advanced-security]

detekt found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[hannesweilharter]

please fix all warnings first and have a look at the Unit Test Report, there are failing testcases. Not sure if they are related to these changes. Then i can do a review :)

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[rinaschedl]

@hannesweilharter please start with CodeReview.
the issue on the Quality Gate is discussed with Thomas and I shall ingnore it for now. There will be a ticket for the Action Faktory because to change the warnings, you have also some changing to the Unit Tests necessary and the workload is relativly high, therefor we changed the ActionFactory back, so you see the warnings but the tests mostly pass now. The 2 failing Tests has nothing to too with the changes I made in the code, so far I can see, so I guess there one of the flanky ones? Lokal all Tests passed, exept some of them who Thomas confirmed are broken. So we should be good.
Thanks
Katharina