Stdout standardization with output formatter

[amydevs]

Description

This PR fixes all the CLI stdout inconsistencies, this is kind of tedious and not critical at the moment though.

Changelog

• agent
  • CommandStatus - versionMetadata is no longer spread into parent object with JSON format.
  • CommandBootstrap - Now uses dict format to output the recoveryCode.
• identities
  • CommandAuthenticate - Now uses dict format
  • CommandClaim - Dict Output, JSON format is now of type { claimId: string; url?: string }.
  • CommandInvite - Feedback is now moved to logger.info so that it goes to stderr
  • CommandList output should be reconsidered due to nested structure. *
  • CommandSearch and CommandGet need streamlining in terms of their output *
• keys
  • CommandCert - Uses dict format
  • CommandCertchain - The message at the start is no longer included.
  • CommandEncrypt - Raw format
  • CommandDecrypt - Raw format
  • CommandSign - now uses camelcase for non-json formats
  • CommandVerify - now uses camelcase for non-json formats
  • CommandPublic, Private, and Pair will need to have further consideration due to nested structure. *
• nodes
  • CommandClaim - Stderr feedback and stdout of success *

Dict Format

This PR also implements changes to the dict format that allows for nesting.

Changes made to commands with this:

agent/CommandStatus

status                  LIVE
pid                     90556
nodeId                  vq3pk7bip927v2ivk7457p5g7b4q3ad0jksqrkv9rfkhl31l1ukng
clientHost              ::1
clientPort              33179
agentHost               ::
agentPort               35454
upTime                  9
startTime               1711068204
connectionsActive       2
nodesTotal              8
version                 1.2.1-alpha.50-1-1
sourceVersion           1.2.1-alpha.50
stateVersion            1
networkVersion          1
versionMetadata  
  version               0.2.3
  commitHash            9275aa5d0d5470e9e586a6fbbdc8ca150c37e5aa
  libVersion            1.2.1-alpha.50-1-1
  libSourceVersion      1.2.1-alpha.50
  libStateVersion       1
  libNetworkVersion     1

identities/CommandList

gestalt
  actionsList       notify
  identities 
    github.com:amydevs
  nodeIds    
    vq3pk7bip927v2ivk7457p5g7b4q3ad0jksqrkv9rfkhl31l1ukng
gestalt
  actionsList       scan
  identities 
    github.com:amydevs
  nodeIds    
    vq3pk7bip927v2ivk7457p5g7b4q3ad0jksqrkv9rfkhl31l1ukng

notificiations/CommandRead

notificiation
  data  
    message test message 1
    type    General
  iat       1711063520.438
  isRead    true
  iss       vmqmqq9h4jgduaeifep1nko1j2uebgg0uh48sc4fl9upqdsijjmf0
  sub       voeo52qencdh720o084mlfpgb1st09vjca0ti9qvm6e0p19ma316g
  typ       notification
notificiation
  data  
    message test message 2
    type    General
  iat       1711063520.438
  isRead    true
  iss       vmqmqq9h4jgduaeifep1nko1j2uebgg0uh48sc4fl9upqdsijjmf0
  sub       voeo52qencdh720o084mlfpgb1st09vjca0ti9qvm6e0p19ma316g
  typ       notification

Issues Fixed

• Related Standardise STDOUT output for CLI commands #22 (doesn't implement verbosity options)
• dict Format Nesting #158

Tasks

• 1. Fix all necessary list formatted outputs to just be strings.
• 2. Fix all necessary list formatted outputs to just be dicts.
• 3. Fix json formatted outputs to return structured POJO rather than just an array with the message itself.
• 4. Implement nesting in dict format
• 5. Fix related tests.

Final checklist

• Domain specific tests
• Full tests
• Updated inline-comment documentation
• Lint fixed
• Squash and rebased
• Sanity check the final build

[ghost]

👇 Click on the image for a new way to code review

Legend

[CMCDragonkai]

This can be incrementally cherry-picked? Or will you do it one go?

[CMCDragonkai]

Cherry pick relevant commits back to staging @amydevs

[amydevs]

the first two commits have been cherrypicked into staging, remember to rebase after

[CMCDragonkai]

You should rebase this PR if you've cherrypicked, since then this will be left with just 1 commit! Otherwise it will be confusing.

[CMCDragonkai]

There's still a problem here: #124 (comment)

[CMCDragonkai]

This needs rebase to be ready to go. I think this week @amydevs you're back on PK #40.

[CMCDragonkai]

Can you expand the task list so we know how close we are finishing this?

[CMCDragonkai]

@amydevs where's the counter?