Marking SyncTriggers [RequiresRunningHost] (#9904)

[mathewc]

Addresses #9904. Recently in PR #9898 we enforced a running host for FlexConsumption sync trigger operations, which allowed us to reliably include extended host config info in the sync payload. It was a TODO to address this for all SKUs after we reviewed the metrics we added in that PR (host.synctriggers.hostnotinitialized) to determine how safe the change would be.

The metric has been out for several releases now, and we now have data showing that about 98% of sync operations are performed on a running host already (query below).

Will backport to in-proc as well.

let _start = ago(3h);
let syncTriggersTotalCount = toscalar(All("FunctionsMetrics")
| where PreciseTimeStamp > _start
| where parse_version(HostVersion) >= parse_version("4.33.2.2")
| where EventName == "host.synctriggers.invoke"
| summarize sum(Count));
let nonInitializedSyncCount = toscalar(All("FunctionsMetrics")
| where PreciseTimeStamp > _start
| where EventName =~ "host.synctriggers.hostnotinitialized"
| summarize sum(Count));
print UnInitializedSyncPercentage=100*round((1.0*nonInitializedSyncCount)/syncTriggersTotalCount, 4);

Pull request checklist

IMPORTANT: Currently, changes must be backported to the in-proc branch to be included in Core Tools and non-Flex deployments.

• Backporting to the in-proc branch is not required
  • Backport PR: Marking SyncTriggers [RequiresRunningHost]. (Addresses #9904) (#10225) #10233
• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)