[compute] fix: background worker that collects installed extension metrics now updates collection interval

[thesuhas]

Problem

Previously, the background worker that collects the list of installed extensions across DBs had a timeout set to 1 hour. This cause a problem with computes that had a suspend_timeout > 1 hour as this collection was treated as activity, preventing compute shutdown.

Issue: https://github.com/neondatabase/cloud/issues/30147

Summary of changes

Passing the suspend_timeout as part of the ComputeSpec so that any updates to this are taken into account by the background worker and updates its collection interval.

[github-actions]

8481 tests run: 7898 passed, 0 failed, 583 skipped (full report)

---

Flaky tests (2)

Postgres 17

• test_compute_pageserver_connection_stress: debug-x86-64-without-lfc

Postgres 16

• test_sharding_split_failures[failure13]: release-arm64-with-lfc

Code coverage* (full report)

• functions: 32.1% (9026 of 28138 functions)
• lines: 48.4% (80247 of 165951 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
0574ecc at 2025-06-18T00:11:58.558Z :recycle:}

[tristan957]

What is the justification for the atomicity?

[tristan957]

Passing the suspend_timeout as part of the ComputeSpec so that any updates to this are taken into account by the background worker and updates its collection interval.

Where is the code for this?

[thesuhas]

Passing the suspend_timeout as part of the ComputeSpec so that any updates to this are taken into account by the background worker and updates its collection interval.

Where is the code for this?

There's a PR on control plane side: https://github.com/neondatabase/cloud/pull/30318

The updation logic is here (for the worker) and the actual value is updated in reconfigure

[thesuhas]

What is the justification for the atomicity?

The interval is in an Atomicu64 and you need to take a lock to read/write to it. Docs