[CRE-6595] base engine decoupling

[agparadiso]

Description

This pr is the first smallest effort to decouple the engine.

• Introduces a WorkflowEngine interface
• decouples the current/legacy engine.go into base_engine (common behavior) and engine.go behavior only valid for that engine
• introduces an CoordinatedEngine that reuses the base_engine and reflects the new engine we are building in which is execution focus only.

Deployment Validation: existing canaries
This change does not alter behavior, the new engine is still not wired. so having existing canaries 🟢 should be enough

CRE-6595

Requires

Supports

[github-actions]

I see you updated files related to core. Please run make gocs 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.

[github-actions]

✅ No conflicts with other open PRs targeting develop

[trunk-io]

   

View Full Report ↗︎ ⋅ Docs

[cl-sonarqube-production]

Quality Gate passed

Issues
5 New issues
6 Fixed issues
0 Accepted issues

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

See analysis details on SonarQube