⭐ implement StoreResults for resources data

[arlimus]

This extends the proto to store resources data directly. This is the next step in the data recordings journey that makes this data available to upstream targets. We are starting our journey in v10, so this is still behind a feature-flag for now.

1. The recording interface moves to LLX, which also defines the runtime. This allows anyone to request the recording layer from the runtime and standardizes setters/getters.
2. StoreResultsReq is extended to support resources recording data via the new resources field. To avoid confusion, the data field has been renamed to query_data, because it captures MQL query data only. The StoreQueryData method was adjusted analogously.
3. The implementation of recordings stays with runtime for now, analogous to runtime itself having a proto/implementation split
4. The feature-flag is StoreResourcesData. Only when it is active will scan results be sent upstream. We continue to not send shell and run data by default. I think we may want to consider sending these but may want to think about a CLI flag to explicitly send data to avoid unwanted side-effects. scan semantically already sends data up, so users expect it to behave this way.
5. The new proto message ResourceRecording captures all recording data for each resource and was adopted from the previous recording implementation (where it was non-proto).

Follow-ups:

As this is only the start, there are 2 vital things before we can spread this more broadly. These have to be done in the v10 timeframe before the feature becomes default:

1. Implement this analogously for cnspec
2. Dedupe resources and query data. We currently duplicate query and recording data, which is annoying.

[github-actions]

Test Results

742 tests  ±0   742 ✅ ±0   12s ⏱️ ±0s
 83 suites ±0     0 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 25a4108. ± Comparison against base commit b120ab4.

This pull request removes 3 and adds 3 tests. Note that renamed tests count towards both.

go.mondoo.com/cnquery/v10/llx ‑ TestSuccess/2024-01-21_23:21:04.710718129_+0000_UTC_m=+0.000878042
go.mondoo.com/cnquery/v10/llx ‑ TestTruthy/2024-01-21_23:21:04.710718129_+0000_UTC_m=+0.000878042
go.mondoo.com/cnquery/v10/llx ‑ TestTruthy/2024-01-21_23:21:04.710718129_+0000_UTC_m=+0.000878042#01

go.mondoo.com/cnquery/v10/llx ‑ TestSuccess/2024-01-23_09:09:21.809737613_+0000_UTC_m=+0.009860502
go.mondoo.com/cnquery/v10/llx ‑ TestTruthy/2024-01-23_09:09:21.809737613_+0000_UTC_m=+0.009860502
go.mondoo.com/cnquery/v10/llx ‑ TestTruthy/2024-01-23_09:09:21.809737613_+0000_UTC_m=+0.009860502#01

♻️ This comment has been updated with latest results.

[chris-rock]

Very nice improvement @arlimus Just added one comment.

[chris-rock]

While there is no technical reason, I'd like to do avoid the rename for now. Can we keep the old name for the field and just extend the comments?

[arlimus]

yes, happy to adjust it

[chris-rock]

Thank you @arlimus