Trim comments and simplify ad-hoc JSON docs per review

Shorten dependency and test comments, drop issue references, and remove
output-format details and the mention of unavailable operators from the
ad-hoc JSON functions documentation (PR #6645 review).

pipeline-manager: use runtime status details for connector stats

Instead of the manager polling all pipelines every GET request for its
list when using the `status_with_connectors` selector, instead
incorporate the connector stats into the runtime status details. The
details are regularly updated by the runner as it does its `/status`
checks. As such, it will take some time for the latest connector stats
to show up after this change (approximately between 1-15 seconds). At
the cost of this slight staleness, the latency of the GET request for
the list of pipelines with that selector will be significantly reduced
(up to 10x faster is observed).

`StorageStatusDetails` is now the type shown in the API for the
`storage_status_details`, instead of the generic JSON value type.
The same for `RuntimeStatusDetails`.

Backward incompatibility notes:
- Pipelines of older versions will continue to have their connector
  stats shown as before. After the user base has migrated past this
  change, the GET request fetching fallback can be removed.
- Runtime status details were directly used for the approval diff. Now,
  if this is present (during the `AwaitingApproval` runtime status), it
  is located at: `deployment_runtime_status_details.approval_diff`.
  The API converts automatically the old JSON values into the JSON
  matching the strongly typed `RuntimeStatusDetails`.

The Web Console and `fda` clients are adjusted to read the approval diff
from the new nested location.

Co-authored-by: Karakatiza666 <bulakh.96@gmail.com>
Signed-off-by: Karakatiza666 <bulakh.96@gmail.com>
Signed-off-by: Simon Kassing <simon.kassing@feldera.com>

[connectors]: read UC-Uniform/Iceberg column-mapped tables by field-id

Bump the delta-rs fork to 9a58fbef, which resolves columnMapping.mode=id
columns by Parquet field-id rather than physical name. Without it, reading a
UC-Uniform-over-Iceberg table fails with `col-<id> is missing from the physical
schema`. Add a snapshot-read regression test (fixture + e2e).

Signed-off-by: Swanand Mulay <73115739+swanandx@users.noreply.github.com>

[SQL] Implement INTERSECT/EXCEPT ALL

Signed-off-by: Mihai Budiu <mbudiu@feldera.com>

pipeline-manager: deprecate unstable feature `cluster_monitor_resources`

The backing (Kubernetes) resources information is now enabled by default
for the cluster monitoring events. It can still be disabled by passing
`--disable-cluster-monitor-resources` as argument.

[SQL] Generalize optimization rule for MAX(CASE WHEN expression THEN …

…1 END)

Signed-off-by: Mihai Budiu <mbudiu@feldera.com>

Address review comments

Signed-off-by: Mihai Budiu <mbudiu@feldera.com>

[adapters] Journal replay respects transaction boundaries.

With the introduction of transactions, the model of computation changed so that
the circuit now produces one output per transaction rather than per step. As a
result the existing journal replay mechanism that runs each input step in a
separate transaction is only correct assuming that the original inputs were
also ingested with a step per transaction. But even that is no longer true
after the introduction of streaming exchange, which can cause a transaction
processing the exact same input take more or fewer steps than the original run
of the program. This broke the validation mechanism that assumed that step
numbers during recording and replay should match precisely.

The solution that this commit implements has repa

- The journal records transaction boundaries in addition to individual steps.
- The replay mechanisms breaks up the sequence of replayed input steps into
  transactions and commits each transaction at exactly the recorded boundary.

This restores the invariant the the outputs of the circuit during replay are
identical to the outputs produced while processing the same inputs before the
failure.

As a side effect of this fix, we also save the last transaction number as part
of the checkpoint, so after restart the circuit will resume contigous
transaction count.

Signed-off-by: Leonid Ryzhyk <ryzhyk@gmail.com>

cargo: update `quinn` and `quinn-proto`

Done using `cargo update quinn`.

- `quinn`: v0.11.8 -> v0.11.11
- `quinn-proto`: v0.11.14 -> v0.11.15

Signed-off-by: Simon Kassing <simon.kassing@feldera.com>

[SQLLIB] Rename truncate -> trunc

Signed-off-by: Mihai Budiu <mbudiu@feldera.com>