Fix UI and TCP reset test races and stale CI reports

[andre487]

Tests and report publication could fail nondeterministically during CI and release builds:

• Profile-selection UI tests clicked before the asynchronous configuration load published the active profile. Wait for the profile label before clicking in both affected tests.
• The local TCP reset test closed the accepted socket before client Dial completed. Synchronize the server reset after successful Dial so both HTTPS and MASQUE exercise a real RST during Read and verify target-scoped diagnostics. This also fixes the test failure that stopped the v1.1.2 artifact build.
• CI reruns retained duplicate JUnit artifacts with the same name, so the reporter combined an earlier failure with a later successful result. Replace matching JUnit artifacts on upload for all suites.

Validation:

• JDK 21, Fastlane-targeted MainScreenUiTest: 13 tests passed.
• bundle exec fastlane android native_tests: 224 tests passed with the race detector.
• go test -race ./mobile -run '^TestLocalResetNeverMarksProxyFailure$' -count=100: all 100 runs passed.
• Confirmed overwrite is supported by upload-artifact v7; git diff --check passed.

Application networking behavior is unchanged. The existing v1.1.2 tag does not include this fix; rerunning its artifact workflow would still test the old source.

APK artifacts

• Download debug APK — signed with the disposable Android debug key
• Download unsigned release APK — verified unsigned

Built from commit 02441f00 by CI run #319.
Artifacts expire after 14 days. Neither APK uses the MegaProxy release key.