Expose parent and root execution in describe call

[Sushisource]

What was changed

Added parent/root wf info to describe

Looks like:

 Execution Info:
          WorkflowId            0195ca09-b69b-7e44-9a65-1117d2397586_5
          RunId                 0195ca09-b6a1-78a2-8b45-0daf88dccf3a
          Type                  DevWorkflow
          Namespace             default
          TaskQueue             a08916ee-28d6-4452-b662-a3cbb219dd13
          AssignedBuildId        
          StartTime             now
          CloseTime             now
          ExecutionTime         now
          SearchAttributes      map[BuildIds:metadata:{key:"encoding"  value:"json/plain"}  metadata:{key:"type"  value:"KeywordList"}  data:"[\"unversioned\",\"unversioned:41011f52e0e0155ca1113ec603b7f2ae\"]"]
          StateTransitionCount  4
          HistoryLength         5
          HistorySize           830
          ParentExecution       {"workflowId":"957a44a6-bea0-45b5-be0e-cab73a4351d3","runId":"0195ca09-b69b-7e44-9a65-1117d2397586"}
          RootExecution         {"workflowId":"957a44a6-bea0-45b5-be0e-cab73a4351d3","runId":"0195ca09-b69b-7e44-9a65-1117d2397586"}
        Extended Execution Info:
          CancelRequested    false
          OriginalStartTime  now
        
        Results:
          RunTime         0s
          Status          COMPLETED
          Result          "done"
          ResultEncoding  json/plain

Why?

Checklist

1. Closes
   [Feature Request] Expose root workflow execution #763

2. How was this tested:
   Added test

3. Any docs updates needed?

[cretz]

I think 4 fields of ParentWorkflowId, ParentRunId, RootWorkflowId, and RootRunId would look a bit better on text output here (all being strings and having cardOmitEmpty too)

[Sushisource]

Sure, I can do that. Ideally we would make it easier to recursively text-ify a struct with indents, that would be ideal, but when I've tried that before it was more work than I wanted to invest at the moment.