feat: bump to PostgREST v14.17

[laurenceisla]

What kind of change does this PR introduce?

Upgrades PostgREST to v14.17

[laurenceisla]

All the smoke tests are passing (Aug 14)...:

https://github.com/supabase/supadev/actions?query=actor%3Alaurenceisla+branch%3Amaster++

Except for the pause-restore one:

https://github.com/supabase/supadev/actions/runs/31774402391

This is only failing for v17 x86_64 and v17 oriole arm and I see that there were similar issues on previous tests, for example:

https://github.com/supabase/supadev/actions/runs/31624786149

Hey @dliappis, do you have an idea why it would be failing?

[dliappis]

Hey @laurenceisla

Yes, the problem you've noticed isn't due to your PR. Every run of supadev's pause-restore smoke tests since Aug 10 has failed the same way (the last green one was Jul 28), because the necessary platform pin bump (to unblock every other test) included platform#36092 (78bf7c9): this commit now executes a final logical dump before pausing a project — and in our test environment that dump has no permission to write to S3, so it retries for ~7 minutes before giving up. A pause that used to take ~2 minutes now takes ~9.

The x86 variant failed for a different reason: the pause actually worked — the project went INACTIVE at 15:37:07 — but supadev didn't notice, because it holds a single 10-minute login token and only checks every 60 seconds, so the first check after the pause finished came back 401 JWT failed verification and it just kept retrying for 5.5 hours until GitHub killed the job at its 6-hour limit.

The oriole leg is a separate problem: OrioleDB pauses through a different code path that has no fallback when the dump fails, so that one really did get stuck.

All these are supadev issues for us to fix, not yours — the two legs that passed in your run hit the exact same S3 error — so none of this blocks the PostgREST v14.17 bump.