Normalize CLI outputs

[maximerety]

Problem(s)

The outputs of various command lines (https://wolverinefx.net/guide/command-line) are a bit inconsistent.

For example in a test project:

❯ dotnet run -- resources statistics

[...]

Resource Statistics
┣━━ Wolverine
┃   ┗━━ Envelope Storage
┃       ┗━━ ┌───────────────────┬────────┐
┃           │ Envelope Category │ Number │
┃           ├───────────────────┼────────┤
┃           │ Incoming          │ 0      │
┃           │ Scheduled         │ 0      │
┃           │ Outgoing          │ 0      │
┃           └───────────────────┴────────┘
┗━━ WolverineTransport
    ┗━━ PostgreSQL Transport
        ┗━━ ┌────────────────┬───────┬───────────┐
            │ Name           │ Count │ Scheduled │
            ├────────────────┼───────┼───────────┤
            │ <some>_channel │     0 │         0 │
            └────────────────┴───────┴───────────┘

vs.

❯ dotnet run -- storage counts

[...]

Persisted Enveloper Counts
┌─────────────┬───────┐
│ Category    │ Count │
├─────────────┼───────┤
│ Incoming    │     0 │
│ Outgoing    │     0 │
│ Scheduled   │     0 │
│ Dead Letter │     0 │
└─────────────┴───────┘

In the first case, we do not print the Dead Letter, and the categories are printed in a different order than in the second.

Similarly, the administration APIs do not report the Dead Letter category but display the number of Handled messages, which neither of the command-line interfaces does.

Proposal

In this merge request, I propose to align all outputs and display all info available.

Notes:

• Changes are added in separate commits for clarity, but they could easily be squashed in a single commit;
• I picked a somewhat arbitrary order for the categories, it can be changed if you think another order makes more sense.

What do you think?

[jeremydmiller]

"What do you think?" - I think this is helpful and I'm thankful you took the time?

Do you want to do anything more, or should I take it in now? I'm trying to get a 5.3 out maybe by the end of this week, but there's always another release coming soon.

[maximerety]

Do you want to do anything more, or should I take it in now? I'm trying to get a 5.3 out maybe by the end of this week, but there's always another release coming soon.

I don't intend to push anything else before the end of the week, so please go ahead 🙂
Thanks.

[maximerety]

@jeremydmiller I just rebased on top of main to keep the branch up to date (no conflicts anyway).