fix(ci): Stop using multiple jobs for quick Google Cloud tests

[teor2345]

Motivation

This PR only uses multiple CI jobs for the full sync tests.
All the other test run in a single "Run" job.

If the SSH errors in these tickets are related to the number of ssh connections we make, this should reduce our CI error rates due to:

• gcloud ssh: Connection reset by peer #5494
• Fix "Connection closed by remote host" error on Google Cloud ssh #5069
• and possibly Fix "the resource was not found" instance errors in CI #5366

But it doesn't actually fix these bugs. (Unless the cause is an undocumented Google Cloud inbound SSH connection rate-limit.)

Solution

• Add a new parameter for long tests, and only enable it for the full sync test
• Remove a job that's a duplicate of the "Run" job
• Remove unused steps and whitespace

Review

@gustavovalverde might be the best person to review this PR.

Reviewer Checklist

• Will the PR name make sense to users?
  • Does it need extra CHANGELOG info? (new features, breaking changes, large changes)
• Are the PR labels correct?
• Does the code do what the ticket and PR says?
• How do you know it works? Does it have tests?

[teor2345]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated

[teor2345]

@Mergifyio update

[mergify]

update

✅ Branch has been successfully updated