compute/sql_exporter: Bump max WSS window from 1h -> 3h

[sharnoff]

Problem

ref neondatabase/cloud#22214.

For larger workloads, 1-hour working set size windows may not be enough to hold the working set size (and so, autoscaling may not have enough information to do a good job scaling LFC). I'm not sure what the right value is, but 3 hours seems like a reasonable increase.

Summary of changes

Concretely, this:

1. Changes the normal (public) exporter to add a new 3-hour working set size label onto the existing 5-minute, 15-minute, and 1-hour values.

2. Extends the range on the autoscaling exporter from 1..60 minutes to 1..180 minutes -- keeping the same density, just 3x longer.

---

I'll try using the compute image produced by this PR on some larger workload before merging, to see if any issues pop up.

[github-actions]

7121 tests run: 6824 passed, 0 failed, 297 skipped (full report)

---

Flaky tests (1)

Postgres 17

• test_timeline_archival_chaos: release-arm64

Code coverage* (full report)

• functions: 31.3% (8400 of 26877 functions)
• lines: 48.0% (66688 of 139059 lines)

* collected from Rust tests only

---

_{The comment gets automatically updated with the latest test results
8b11e3b at 2024-12-25T04:54:30.906Z :recycle:}