v0.4.0

Added

• term-rest-client -gui: a browser interface on the same workspace, embedded in the
  binary (about 370 KB). Requests run in the Go process, so there's no CORS. It has
  request tabs, the collections tree, variables and environments, live streams, a
  WebSocket log and composer, the GraphQL schema browser, a JSON tree view, history,
  code snippets, cURL and Postman import, a command palette, and light and dark themes.
  It listens on 127.0.0.1 on a free port by default; -port asks for a port (a busy one
  falls back to a free one), -lan also listens on the network and prints a link per
  address, and -no-open doesn't start a browser. A per-run key, a SameSite cookie and
  Host and Origin checks keep other sites from using it.
• Copy from the response pane: c copies the body; y opens a menu with the body raw or
  as pretty JSON, response and request headers as text or JSON, the full response (like
  curl -i), and stream events or WebSocket messages as JSON.
• Ctrl+T opens the GraphQL schema browser. F6 still works, but on Macs it turns on
  Do Not Disturb unless fn is held. The README has a macOS section on function keys
  and on making Option work as Alt in Terminal.app and iTerm2.

Changed

• For a WebSocket request the Body tab is now called Message and drops the HTTP body
  type picker (JSON, Form, ...), which never applied to messages. A note says the text
  is sent as is when the connection opens, and the example shows plain text or JSON.
• The GraphQL schema browser has a Details pane (description, arguments, the result
  type's fields, and the query it would write). Enter, Space and clicks now open and
  close fields instead of replacing the query, and i inserts the query, also from
  nested fields.

Fixed

• An empty GraphQL body showed a JSON example ({"name": "{{name}}"}) as its
  placeholder, which looked like a query that was already there. The Query and
  Variables editors now show GraphQL examples and mention F6, and sending an empty
  query says to type one or press F6.
• Errors before sending (an empty query, a bad URL, a failing pre-request script) showed
  "No Environment" even with an environment selected.