fix: don't drop networkVolume and networkVolumeId in pod get

[ajpower]

Summary

runpodctl pod get $pod --include-network-volume does not actually return network volume info despite passing the required params to the underlying REST API. The root cause is that the Pod struct is missing these fields, so they are discarded upon deserialization. This PR adds the missing fields and closes #291.

Testing

I created a pod nsr02fbf61si3n with a network volume attached. Without the change, runpodctl pod get nsr02fbf61si3n --include-network-volume | jq '.networkVolume' returns null. With the change, bin/runpodctl pod get nsr02fbf61si3n --include-network-volume | jq '.networkVolume' returns

{
  "dataCenterId": "EU-CZ-1",
  "id": "niq6cdm1yy",
  "name": "principal_pink_tern",
  "size": 10
}

Note that with the change, pod get always returns a networkVolumeId (if a network volume is present) whether --include-network-volume is passed or not. I believe this is the desired behaviour since the inclusion of the networkVolumeId comes for free.

Related issue

While investigating this issue, I discovered another bug: uptimeSeconds seems to always be zero. Pod nsr02fbf61si3n has an uptime of over an hour, yet runpodctl pod get nsr02fbf61si3n | jq '.uptimeSeconds' returns 0. I believe the root cause is that the GraphQL API returns

{ "uptimeSeconds": 0, "runtime": { "uptimeInSeconds": 4026 } }

but the CLI takes uptimeSeconds instead of runtime.uptimeInSeconds.