fix(cli): Fixes bug with command 'ps -x' (sudo)

[sbosio]

Description

The command

heroku sudo ps -x -a <private-space-app>

fails currently for Private Space apps because the extended property on the JSON response has many of its properties set to null, giving a TypeError when trying to coerce the null port number to a string.

Here we correct the type definition, allowing for null values on all of the extended properties and handling that case appropriately when building the output table display.

SOC2 Compliance

Slack thread for reference
GUS Work Item

[eablack]

Hmm, I'm still seeing an error when i try to run this with your branch:

is it possible we need to add another optional chain here? https://github.com/heroku/cli/pull/3051/files#diff-5d43d9c03ed768f9c4f93c44502238c8961bba579421ce39c334cbdfe20b1f0eR65

[sbosio]

Hmm, I'm still seeing an error when i try to run this with your branch:

is it possible we need to add another optional chain here? https://github.com//pull/3051/files#diff-5d43d9c03ed768f9c4f93c44502238c8961bba579421ce39c334cbdfe20b1f0eR65

No, the problem is sudo that will parse arguments and build a command again with the right headers, but using heroku and not ./bin/run, thus effectively using the unpatched version of the ps -x command.

Run tests with:

HEROKU_HEADERS='{"x-heroku-sudo": true}' ./bin/run ps -x -a particleboard-staging

It will require a few times for your 2FA method, but ultimately it will work.

[eablack]