maxctrl2 "list servers" does not render Status Info despite non-empty reason data

Summary
--------
maxctrl2's "list servers" command always shows an empty Status Info
column, even when the underlying server status has non-empty reason
data. The same server, queried at the same time with classic maxctrl,
correctly shows the reason content in Status Info. maxctrl2 appears to
have a rendering gap that drops the reason array when building this
column, while the "show server" endpoint returns the data correctly
in both tools' backing data.

root@mxs:~# maxctrl list servers

maxctrl2 list servers

┌─────────┬────────────┬──────┬─────────────┬────────┬─────────────┬─────────────┬─────────────────┐

│ Server  │ Address    │ Port │ Connections │ Status │ Status Info │ GTID        │ Monitor         │

├─────────┼────────────┼──────┼─────────────┼────────┼─────────────┼─────────────┼─────────────────┤

│ server1 │ 10.0.0.101 │ 3306 │ 0           │ Write  │ Primary     │ 0-1-3949183 │ MariaDB-Monitor │

└─────────┴────────────┴──────┴─────────────┴────────┴─────────────┴─────────────┴─────────────────┘

┌─────────┬────────────┬──────┬─────────────┬────────┬─────────────┬─────────────┬─────────────────┐

│ Server  │ Address    │ Port │ Connections │ Status │ Status Info │ GTID        │ Monitor         │

├─────────┼────────────┼──────┼─────────────┼────────┼─────────────┼─────────────┼─────────────────┤

│ server1 │ 10.0.0.101 │ 3306 │ 0           │ Write  │             │ 0-1-3949183 │ MariaDB-Monitor │

└─────────┴────────────┴──────┴─────────────┴────────┴─────────────┴─────────────┴─────────────────┘

root@mxs:~#

Steps to Reproduce
-------------------
1. Set up a server with a non-empty status reason (e.g. a Primary
server, which reports reason: ["Primary"]).
2. Run both of the following against the same server at the same time:
maxctrl list servers
maxctrl2 list servers
3. Compare the Status Info column between the two outputs.

Expected Result
----------------
maxctrl2 should render the same Status Info content as maxctrl, since
both draw from the same underlying reason data (confirmed via maxctrl
show server output showing a populated reason array).

Workaround
-----------
None within maxctrl2 itself. Customers who need this data can cross
check with classic maxctrl, or use maxctrl2 show server <name> to see
the full "reason" data directly (JSON output), instead of the list
servers table.

Additional Notes
-----------
Related customer ask (Nokia, Zendesk #244700): in addition to this
rendering bug, the customer has asked whether the old single "State"
field (combining role and status text, e.g. "Slave, Running") could
be restored as a default field in maxctrl2's list servers command,
rather than the current split status/status-info fields.