docker: don't set LD_LIBRARY_PATH

[jcsp]

Problem

This was causing storage controller to still use neon-built libpq instead of vanilla libpq.

Since #10269 we have a vanilla postgres in the system path -- anything that wants a postgres library will use that.

Summary of changes

• Remove LD_LIBRARY_PATH assignment in Dockerfile

[rahulinux]

Should we set it explicitly rather than using the default setting for the storage controller? I suspect that changing the default might break something else. https://neondb.slack.com/archives/C033RQ5SPDH/p1736416908939979?thread_ts=1736413779.069519&cid=C033RQ5SPDH

[rahulinux]

Should we set it explicitly rather than using the default setting for the storage controller? I suspect that changing the default might break something else. neondb.slack.com/archives/C033RQ5SPDH/p1736416908939979?thread_ts=1736413779.069519&cid=C033RQ5SPDH

discussed here https://neondb.slack.com/archives/C033RQ5SPDH/p1736417720516929?thread_ts=1736413779.069519&cid=C033RQ5SPDH

[github-actions]

7286 tests run: 6919 passed, 0 failed, 367 skipped (full report)

---

Flaky tests (3)

Postgres 17

• test_physical_replication_config_mismatch_too_many_known_xids: release-arm64
• test_s3_wal_replay: release-arm64

Postgres 15

• test_parallel_copy: release-arm64

Code coverage* (full report)

• functions: 31.1% (8411 of 27005 functions)
• lines: 47.8% (66780 of 139607 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
5342c0f at 2025-01-09T11:56:19.542Z :recycle:}