Add abstraction of Azos.Sky.Fabric.Fiber - an orchestration context (e.g. result mailslot address) to execute distributed cloud services/units of work

[itadapter]

Processes provide:

1. Unique mutext ID whih can be used for
2. Result/mailslot address for actors
3. Chronicle execution log correlation
4. Management, status tracking
5. Supervisor actors ensure process final state machine transition

This new model supersedes prior art here:
https://github.com/azist/azos/tree/master/src/Azos.Sky.Server/Workers

Process - a global context of the larger task execution, establishes context for multiple instances of asynchronous Todos,
captures the final result of multiple Todos; reacts to Signals

IMPORTANT The system should be able to handle millions of active executing processes (i.e. not keep all in ram), as processes may represent certain business activities, such as a contract execution paused on a customer signature step) etc.. Sharding and Fail-over is 100% required as processes represent the ultimate distributed process supervision orchestration primitive

[itadapter]

  GDID
  GUID

  parent_ID
  priority
  scheduled_time
  
  Creator_User  EntityId
  Create_Origin Atom
  CreateUtc 
  Tenant   string
  ShardKey
    
  Description
  Note

  Namespace   string
  Image  string;// fully qualified exeutable package (e.g. assembly)

  Status
  State  
  
  Result:()

ProcessResources (CPU, Memory, Disk)
ExitResult : Json
Memory(PID, Segment): (ctype, bin[])

[itadapter]

[itadapter]

todo

• Validate State before commiting slots back to shard
• Fiber.WriteLog()... add these methods
• What is the very first current step????

[itadapter]

Need to test case: When BIX atr is forgotten on slot - we need not crash the Fiber... need to review exception types

incorrect, this must crash fiber as it is impossible to handle this otherwise,
the exception may surface only WHEN accessing certain state slot which is not decorated...
so it is a regular fiber exception and program can not continue