Fix flaky Postgres tests

[mtrezza]

New Issue Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.
• I can reproduce the issue with the latest version of Parse Server.

Issue Description

The flaky Postgres tests are currently the most significant bottleneck when it comes to merging PRs:

• More reviewer effort required to restart failing tests
• Longer wait time for contributors to see PRs getting merged
• Increased resource costs (GitHub Action compute time)

While there were other CI/CD related bottlenecks in the past, they have largely been removed over time so that this issue became now the most impactful one.

Solution

Fix the flakiness.

[parse-github-assistant]

Thanks for opening this issue!

• 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

[mtrezza]

@dplewis not sure if that helps with fixing the flaky tests for Postgres, but since we disabled test randomization, there seems to be a recurring pattern of Postgres failing exactly like this: https://github.com/parse-community/parse-server/actions/runs/9973005229/job/27557477165?pr=9209

[dplewis]

Is this for a specific Postgres version? Can I pick up this bounty?

[mtrezza]

I believe I have seen the issue always occurring for the same Postgres version since we disabled the test randomization.

The issue has been created for all flaky tests that are specific to Postgres, but I'm unsure how vast that is, now that the randomizer is off. I guess if you could fix the flaky test from the log above we can close this issue and pay out the bounty, as w/o randomizer it seems to be the only flaky test.

[dplewis]

This test has always been flaky since the introduction of transactions. I would have fixed it years ago if I knew how it worked. Probably @davimacedo knows how to fix it. Also this isn't postgres specific either this can fail for mongo as well.

[mtrezza]

Interestingly, since we disabled the randomizer it seems to be only that specific Postgres version where it fails.

[parseplatformorg]

🎉 This change has been released in version 7.3.0-alpha.3

[parseplatformorg]

🎉 This change has been released in version 7.3.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 7.3.0