fix(proxy): remove postgres notice logs

[conradludgate]

The notice logs don't serve much utility for us for managed connections, so we can remove them.

As a side effect, the notice infrastructure within connection.rs is no longer necessary which allows us to simplify some things.

[conradludgate]

An alternative worth considering is to instead include these notices in the HTTP response.

[cloneable]

An alternative worth considering is to instead include these notices in the HTTP response.

You mean as http2/websocket side-channel or embedding them in the response JSON?

[conradludgate]

In the response JSON, where along side the results: [ ... ] there could be a notices: [ ... ]. I don't know if it's worth the effort though. No one has asked for it either.

[conradludgate]

Websocket connections are not managed by us, and they would get all the notices by default

[github-actions]

7095 tests run: 6797 passed, 0 failed, 298 skipped (full report)

---

Flaky tests (1)

Postgres 17

• test_lr_with_slow_safekeeper: release-arm64

Code coverage* (full report)

• functions: 31.2% (8400 of 26933 functions)
• lines: 47.9% (66678 of 139070 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
1d644b8 at 2025-01-02T17:29:28.625Z :recycle:}