CRE-1714: ring test real workflows

[mchain0]

PR contains:

• fix for the smoke test to handle consensus error with missing wantShards
• fix for the smoke test to properly initiate Arbiter state
• refactor to integrate Store struct to be shared via reference across Ring and ShardOrchestrator (eliminates earlier broken synchronization)
• multiple additional asserts in the smoke test for workflows, consensus round progressing, etc.
• early version of Workflow Registry Syncer extension to call Ring, wait for the consensus and once reached - load and initiate only workflows mapped to the shard
• several other improvements to the E2E sharding flow
• test workflows compilation and deployment (10 workflows, cron-trigger)
• asserting on the mappings
• asserting on the beholder messages for all workflows being executed in expected shards
• rebase with the develop changes to support multiple workflow sources
• optimization: improvement to the workflow registry syncer to communicate with local ringStore when running in shard-0

CRE-1714

[github-actions]

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

• #added For any new functionality added.
• #breaking_change For any functionality that requires manual action for the node to boot.
• #bugfix For bug fixes.
• #changed For any change to the existing functionality.
• #db_update For any feature that introduces updates to database schema.
• #deprecation_notice For any upcoming deprecation functionality.
• #internal For changesets that need to be excluded from the final changelog.
• #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
• #removed For any functionality/config that is removed.
• #updated For any functionality that is updated.
• #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

[trunk-io]

     

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
6 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
2.0% Duplication on New Code

See analysis details on SonarQube

[bolekk]

It looks like all new code is properly feature-flagged in application/delegate/syncer. I don't mind merging it once it's rebased on develop.

[bolekk]

Can you collect those extra params if sharding is enabled and then pass to one shared call to NewWorkflowRegistry()?