9c-main: introduce a new headless to check lib9c development branch's state transition logic backward-compatibility

[moreal]

Description

This issue suggests introducing a new headless which uses the RemoteActionEvaluator feature, to check the lib9c development branch's state transition logic backward compatibility.

Now, lib9c includes all state transition logics (i.e., IAction) in one Assembly so the lib9c development branch must always guarantee its backward compatibility.

And 9c-headless started to support the RemoteActionEvaluator feature. It separates action evaluation logic as a web service from the 9c-headless process. it means it can independently update only the action evaluation logic, without a 9c-headless image bump. It is the point to suggest. Run a new headless with RemoteActionEvaluator and a lib9c-stateservice, then upgrade lib9c-stateservice image periodically to the lib9c repository development branch's latest Docker build. Because the lib9c-stateservice is a stateless web service, I expect it can be upgraded smoothly as other web services do.

Plan (maybe)

• Move the Lib9c.StateService project and related CIs to the planetarium/lib9c repository from planetarium/NineChronicles.Headless.
  • https://github.com/planetarium/NineChronicles.Headless/tree/development/Lib9c.StateService
  • https://github.com/planetarium/NineChronicles.Headless/blob/9830e47675fc29c60a8d1a7d18322d8b44cd286b/.github/workflows/push_docker_image.yml#L63-L80
  • Completed by ci(gh-actions): build Docker image lib9c#2039.
• Introduce the nightly tag and the latest tag for planetariumhq/lib9c-stateservice image.
• Introduce lib9c-stateservice and 9c-headless resource pair. (example permalink).
• Let ArgoCD update the lib9c-stateservice image automatically, periodically.
  • Decide how often to update lib9c-stateservice image to check the actions' backward-compatibility (e.g., every day, every 3 hours).