Make status telemetry available in simulation and fix schema coverage

[tclinkenbeard-oai]

Summary

• Correct the executable status schema and its public reference documentation by removing deleted blob roles and noncanonical storage-engine output aliases.
• Accept the canonical memory-radixtree perpetual-wiggle engine while preserving legacy configuration-input aliases and supported process classes.
• Publish deterministic simulated process, machine, and network telemetry after worker transport binding so simulation exercises the normal production status JSON formatter and retains full reachable schema coverage.
• Correct JSON serialization of unset worker locality attributes so both process and machine status preserve their actual null values.
• Preserve genuinely conditional status fields and omit only scalar map markers that cannot produce coverage events.
• Add focused schema-validation regression coverage and registered status simulations that require complete process and machine telemetry for ssd-1 and memory-radixtree storage configurations while excluding only incompatible Attrition workloads.

Validation

• git diff --check origin/main...HEAD
• clang-format-19 --dry-run --Werror fdbclient/Schemas.cpp fdbclient/include/fdbclient/JsonBuilder.h fdbserver/SimulatedCluster.cpp fdbserver/clustercontroller/Status.cpp fdbserver/workloads/StatusWorkload.cpp
• fdbserver_clustercontroller_test -f /status/json/builder
• fdbserver -r unittests -f /fdbserver/status/schema/
• fdbserver -r simulation -f tests/fast/StatusStorageEngine.toml -s 12648430 -b off -fi off
• fdbserver -r simulation -f tests/fast/StatusPerpetualWiggleEngine.toml -s 12648430 -b off -fi off
• fdbserver -r simulation -f tests/fast/StatusDuringOutage.toml -s 12648430 -b off -fi off
• fdbserver -r simulation -f tests/fast/StatusStorageEngine.toml -s 12648430 -b on -fi on
• fdbserver -r simulation -f tests/fast/StatusPerpetualWiggleEngine.toml -s 12648430 -b on -fi on

[foundationdb-ci]

Result of foundationdb-pr-clang-ide on Linux RHEL 9

• Commit ID: 9822bad
• Duration 0:22:29
• Result: ✅ SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-clang on Linux RHEL 9

• Commit ID: 9822bad
• Duration 0:39:38
• Result: ❌ FAILED
• Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-clang-arm on Linux RHEL 9

• Commit ID: 9822bad
• Duration 0:46:18
• Result: ✅ SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr on Linux RHEL 9

• Commit ID: 9822bad
• Duration 0:48:31
• Result: ❌ FAILED
• Error: Error while executing command: ctest -j ${NPROC} --no-compress-output -T test --output-on-failure. Reason: exit status 8
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-cluster-tests on Linux RHEL 9

• Commit ID: 9822bad
• Duration 1:28:53
• Result: ✅ SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)
• Cluster Test Logs zip file of the test logs (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-macos-m1 on macOS 14.x

• Commit ID: 9822bad
• Duration 1:38:01
• Result: ✅ SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)

[foundationdb-ci]

Result of foundationdb-pr-macos on macOS 14.x

• Commit ID: 9822bad
• Duration 4:32:37
• Result: ✅ SUCCEEDED
• Error: N/A
• Build Log terminal output (available for 30 days)
• Build Workspace zip file of the working directory (available for 30 days)