Improvements to the process and network management commands

[dkovba]

Improves the process and network management commands.

[crosbymichael]

Why are we getting lower fidelity on these error codes? Since we are catching a ContainerizationError it's going to have the original code already as that actually happened. Throwing a new error causes us to lose a bit of information. Is there a reason to do this through this PR?

[dkovba]

We are catching ContainerizationError to convert it to GRPCStatus. Without this conversion, all errors would become generic GRPC internal errors.

[dkovba]

It seems reasonable to implement toGRPCStatus in ContainerizationError to reduce the amount of code for error conversion and to convert all possible errors.

[crosbymichael]

Oh I see now. Many of the codes should map well from cz error to grpc status. You could do something like:

extension ContainerizationError {
    /// Convert the ContainerizationError into a GRPCStatus result.
    var status: GRPCStatus {
        let code: GRPCStatus.Code = {
            switch self.code {
            case .notFound: .notFound
            case .exists: .alreadyExists
            case .unsupported: .unimplemented
            case .unknown: .unknown
            case .internalError: .internalError
            case .interrupted: .unavailable
            case .invalidState: .failedPrecondition
            case .invalidArgument: .invalidArgument
            case .timeout: .deadlineExceeded
            default: .internalError
            }
        }()
        return GRPCStatus(
            code: code,
            message: self.description,
            cause: self
        )
    }
}

[dkovba]

This approach loses the operation context compared to what I've already implemented. However, we can handle more error codes.