feat: Add reason field to notification output

[LangLangBart]

description

The WebUI also shows the user the notification reason¹. In some situations, this may be
useful to the user. This PR would add the reason to the notification output.

Points to consider:

• Where should we display the reason?
  • Currently, it is after the type.
• The magenta dot for unread notifications gets pushed further to the right and may not be visible
  with small terminals or extremely long repo names.
  • One idea would be to truncate the repo names, and add a hidden field with the full repo name, as
    the full name is needed to perform action on it, for example opening it in the browser.
  • Another idea is to move the magenta dot to the very beginning of the notification line or
    after the timestamp.

Footnotes

1. REST API endpoints for notifications - GitHub Docs: Notification Reasons ↩

[meiji163]

great!

[LangLangBart]

Move the unread_symbol to the first field and make the timestamp relative for updates made <24h ago.

---

Long repo names are abbreviated, for example:

• shd101wyy/vscode-markdown-preview-enhanced becomes shd101wyy/vscode-markdown…

---

The reason is now positioned after the number in a subtle gray tone, and the type is
highlighted in white_bold. This reordering and color changes should enhance readability and
optimize what immediately catches the eye.