This could result in telemetry metrics not being submitted if a certain
telemetry client was not active for more than half an hour (could happen
if the activity is very low).

It would also cause unnecessary (but o/wise benign) metric
registrations.

…s; fix racy telemetry log test

updateable_waf: when an ASM_DD config fails to be added to the builder,
restore the initial ruleset if it was removed, matching the existing
restore logic in remove_config.

TelemetryTests: wait for the specific bad_config diagnostic log rather
than any 3 RC logs, avoiding a race where leftover exception logs from
the previous test satisfy the condition before the diagnostic arrives.

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>

Causes flakiness in the tests, as symbolization can take > 10 s.

…sabled

If remote config was disabled, client_init would inform the helper that
remote config is disabled. However, subsequent config_syncs would
neverthless send a remote config path (config_sync doesn't separately
send whether remote config is enabled). The path being non-empty the
helper-rust would deem remote config enabled and create a new service.

In practice, this did not actually result in remote config being
enabled, because sidecar being informed through config that it's
disabled, the shared memory path would not be written to. Neverthless,
this resulted in the creation of extra Service's and extra
initializations of the waf, reflected in a higher number of waf.init
metrics.