CI(deploy): create git tags/releases before triggering deploy workflows

[jcgruenhage]

Problem

When dev deployments are disabled (or fail), the tags for releases aren't created. It makes more sense to have tag and release creation before the deployment to prevent situations like this.

It is not enough to move the tag creation before the deployment. If the deployment fails, re-running the job isn't possible because the API call to create the tag will fail.

Summary of changes

• Tag/Release creation now happens before the deployment
• The two steps for tag and release have been merged into a bigger one
• There's new checks to ensure the that if the tags/releases already exist as expected, things will continue just fine.

[github-actions]

7092 tests run: 6784 passed, 0 failed, 308 skipped (full report)

---

Flaky tests (5)

Postgres 17

• test_cli_start_stop: debug-x86-64
• test_physical_replication_config_mismatch_max_locks_per_transaction: release-x86-64

Postgres 15

• test_prefetch[None]: release-x86-64
• test_pull_timeline[True]: release-x86-64

Postgres 14

• test_pull_timeline[True]: release-arm64

Code coverage* (full report)

• functions: 31.4% (8321 of 26471 functions)
• lines: 47.8% (65386 of 136877 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
bfa9692 at 2024-12-05T16:15:04.623Z :recycle:}

[bayandin]

Good work!
I've added an optional comment, feel free to ignore