Update PostgreSQL 17 from 17rc1 to 17.0

[MMeent]

Problem

Summary of changes

• The PostgreSQL 17 vendor module is now based on postgres/postgres @ d7ec59a63d745ba74fba0e280bbf85dc6d1caa3e, presumably the final code change before the V17 tag.

Checklist before requesting a review

• I have performed a self-review of my code.
• If it is a core feature, I have added thorough tests.
• Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
• If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

• Do not forget to reformat commit message to not include the above checklist

[github-actions]

5064 tests run: 4899 passed, 1 failed, 164 skipped (full report)

---

Failures on Postgres 15

• test_storage_controller_heartbeats[failure4]: release-x86-64

# Run all failed tests locally:
scripts/pytest -vv -n $(nproc) -k "test_storage_controller_heartbeats[release-pg15-failure4]"

Flaky tests (4)

Postgres 17

• test_readonly_node_gc: debug-x86-64

Postgres 16

• test_subscriber_restart: release-x86-64

Postgres 15

• test_timeline_copy[500000]: release-x86-64

Postgres 14

• test_scrubber_physical_gc[None]: release-arm64

Code coverage* (full report)

• functions: 32.1% (7470 of 23246 functions)
• lines: 50.0% (60198 of 120485 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
ec0784d at 2024-09-24T12:07:56.441Z :recycle:}

[arpad-m]

Failure of test_readonly_node_gc is known flakiness of that test link. cc #9071