DLQv2 operator tooling should print categoryID, source cluster, and target cluster instead of internal queue name

[tdeebswihart]

Is your feature request related to a problem? Please describe.

Right now our DLQ tooling dumps the internal DLQ queue name which is not only an implementation detail but not what you need to use the tool. For example:

$ tdbg dlq --dlq-version v2 list
          QUEUENAME          | MESSAGECOUNT
  1_cluster1_cluster2_ETC |            0

Right now this is in the form {dlq-type}_{source-cluster}_{target-cluster}_BLAH but we shouldn't expect our operators to know that.

Describe the solution you'd like

To use our DLQ tooling you need to know:

• The DLQ's type (1 in the above example).
• The source cluster (cluster1)
• The target cluster (cluster2)

Those are the values that should be dumped, so I'd expect something like

DLQ TYPE | SOURCE CLUSTER | TARGET CLUSTER | MESSAGECOUNT
1        | cluster1       | cluster2       | 0

Describe alternatives you've considered

I didn't.