KES Agent Connectivity

[tdammers]

This adds KES Agent connectivity to consensus.

To use a KES Agent to source KES SignKeys and OpCerts, the praosCredentialsSource in the PraosCanBeLeader data structure can now be pointed to a domain socket address where it will look for a KES Agent.

Also covers #1077.

[jasagredo]

I'm unsure if this one should use FsPath instead? cc @jorisdral

[jasagredo]

The use of serdoc-core prevents us from using GHC 9.12.2:

Configuration is affected by the following files:
- cabal.project
- cabal.project.local
Resolving dependencies...
Error: [Cabal-7107]
Could not resolve dependencies:
[__0] trying: kes-agent-0.1.0.0 (user goal)
[__1] trying: template-haskell-2.23.0.0/installed-2522 (dependency of kes-agent)
[__2] next goal: serdoc-core (dependency of kes-agent)
[__2] rejecting: serdoc-core-0.3.0.0 (conflict: template-haskell==2.23.0.0/installed-2522, serdoc-core => template-haskell>=2.16 && <2.23)
[__2] skipping: serdoc-core; 0.2.0.0, 0.1.0.0 (has the same characteristics that caused the previous version to fail: excludes 'template-haskell' version 2.23.0.0)
[__2] fail (backjumping, conflict set: kes-agent, serdoc-core, template-haskell)
After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: template-haskell, serdoc-core, kes-agent