This reverts commit a1ae4fea.

Revert "Refactor iOS integration_test API to support Swift, dynamically add native tests (#88013)" (#88377)

This reverts commit 9e3de9a3.

d58036f45 [quick_actions] Android support only calling initialize once (flutter/plugins#4204) (#88363)

This reverts commit b586695c.

* Bump to Gradle 7 and use Open JDK 11

* Add caches

* Fixes

* Remove org.gradle.java.home

Consolidate duplicated cut/copy/paste/selectall code so it can be done via Actions in the future.

Revert "Revert "Revert "Restores surface size in the postTest of test binding (#87240)" (#87258)" (#87297)" (#88293)

This reverts commit 91f8b6be.

Co-authored-by: Alexander Dahlberg <alexander.dahlberg@sigma.se>

The TapGestureRecognizer in the test named 'TapGestureRecognizer _sentTapDown toString' was not disposed, which was breaking a couple of other tests.
This worked fine when not shuffling the tests as the test was executed last.

Co-authored-by: Alexander Dahlberg <alexander.dahlberg@sigma.se>

Fixes test/animation/animation_controller_test.dart in #85160

Problem:
The test 'animateTo can deal with duration == Duration.Zero' was failing with the following error:

Expected: <0>
Actual: <5>
Expected no animation.
package:test_api expect
package:flutter_test/src/widget_tester.dart 484:3 expect
test/animation/animation_controller_test.dart 511:5 main.

Following line finds 5 transientCallbacks scheduled, while expecting zero, if shuffled with seed 123:

expect(SchedulerBinding.instance!.transientCallbackCount, equals(0), reason: 'Expected no animation.');

This is caused by some other test leaving transientCallbacks scheduled.

Fix:
By disposing the AnimationController after each test, the transientCallbacks get cleaned up.
I chose to dispose all controllers in every test, to make sure there is no risk of leaks.