Track query and datastore cpu usage metrics

[joshua-spacetime]

Description of Changes

Tracks cpu usage metrics in both query and datastore. It does not track wasmtime fuel usage

API and ABI breaking changes

None

Expected complexity level and risk

3

The changes are relatively straightforward, just a lot of plumbing.

Testing

An existing query test was updated to test the query metrics. New tests were added for the datastore.

[Centril]

How does this affect the subscription benchmarks?

[joshua-spacetime]

@Centril the impact for these is negligible.

full-join        time:   [91.830 µs 92.193 µs 92.510 µs]
                 change: [-1.6552% -1.2958% -0.9618%] (p = 0.00 < 0.05)
                 Change within noise threshold.

However once we introduce "bytes scanned" for example, I fully expect the difference will no longer be negligible.

[jsdt]

These metrics look good, though I'm curious about how we will be able to add byte-based read stats.

[gefjon]

Approving as code owner for websocket.rs . Have not checked the rest.

[jsdt]

Adding a metric for bytes inserted is the only datastore-related metric that we still need, but that can be in a different PR.