fix: restore message + phone IDs in list output, clarify direction

[abhiramkast]

Problem

The v2 rewrite dropped the ID column from linq messages list and linq phonenumbers — so an agent (or a human) can't grab an ID to act on a specific message or phone without falling back to --json.

messages list was also confusing:

• The arrow + number (→ +1 (205) 222-2918) was ambiguous — does it mean "sent to" or "sent from"?
• A sent / delivered / read status was shown for every row, but "sent" is meaningless for an inbound message.

messages list --json was leaking the raw SDK envelope (options, response, a duplicated payload) — noisy and coupled to SDK internals.

Solution

• messages list: bring back the message ID (cyan, leftmost, copy-paste ready); switch to absolute timestamps; drop the status column (still in linq messages get); replace the ambiguous arrow with explicit you → +1 (...) / +1 (...) → you.
• phonenumbers: bring back the phone number's UUID before the formatted phone.
• messages list --json: emit just { messages, next_cursor } instead of the whole SDK wrapper.

Notes

Other commands still leak the SDK envelope in --json. Follow-up PR will clean those up uniformly.

[jflayhart]

🎉 This PR is included in version 2.0.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀