Add resource consume test funcs

[shayanh]

Problem

Building on #5875 to add handy test functions for autoscaling.

Resolves #5609

Summary of changes

This PR makes the following changes to #5875:

• Enable neon_test_utils extension in the compute node docker image, so we could use it in the e2e tests (as discussed with @kelvich).
• Removed test functions related to disk as we don't use them for autoscaling.
• Fix the warning with printf-ing unsigned long variables.

[github-actions]

2436 tests run: 2319 passed, 0 failed, 117 skipped (full report)

---

Code coverage (full report)

• functions: 56.0% (12855 of 22974 functions)
• lines: 82.6% (69546 of 84170 lines)

---

_{The comment gets automatically updated with the latest test results
1b6f878 at 2024-02-14T18:41:33.959Z :recycle:}

[skyzh]

Depending on your use case, maybe you will need to add trusted = true at the end of the control file? trusted = true means that the extension will be loaded using superuser permission even if the one creating the extension is not a superuser.

https://github.com/neondatabase/neon/blob/main/pgxn/neon_test_utils/neon_test_utils.control

• If you don't expect our end-user to use it -> don't add trusted = true so that it cannot be loaded on production environment, but you might need to find a way to load the extension in e2e test b/c IIRC the cloud e2e test uses the same permission as the end user so that you may not be able to load it...?
• If you expect our end-user to use it -> add trusted = true. But I think this seems like an internal module and shouldn't be used by users.

Rest LGTM

[shayanh]

@skyzh I already added trusted = true to the control file. Needed that bc e2e tests uses the same permission as a normal user.