[Gorka Gonzalo (d0ubl3g)]

Fixed

• The README now says that the MSI installs for all users and needs an administrator. Run silently
  by a standard user it fails with exit code 1603 on Windows 11 and 1625 on Windows Server 2022
  (measured on 0.6.0); standard users without administrator rights should use the zip or Scoop.
• A certificate that is not trusted (unknown issuer, expired, wrong name) is no longer retried as a
  transient connection failure. The CLI makes one TLS handshake and exits with 7 and the same
  message as before, instead of making three. Refused, reset and timed-out connections and
  502/503/504 are still retried.
  (#245)
• A 403 with MODULE_NOT_ENTITLED (the tenant's plan does not include the module a command
  reads, or the compliance framework is not enabled) now says so, names the scope the server
  reports, and tells the user that a tenant administrator must add the module or enable the
  framework. It still exits with 4. It used to read as a missing scope, and with no scope listed
  the generic message ended in needs: ., which now reads sensibly.
• That 403 now names the module the plan lacks or the compliance framework that is not enabled
  when the server says which, with a hint to add the module or enable the framework, instead of
  guessing between the two. An older server gets the same message as before.
  (#249)
• The README's DNF setup block wrote an empty /etc/yum.repos.d/hodeishield.repo, so dnf install hodeishield found no package. The file now gets the repository configuration.
• On Windows, login with its output piped (for example hodeishield login 2>&1 | ForEach-Object { "$_" }) did not return until the browser exited. The browser inherited the pipe, so the reader
  waited for it. login now stops the browser from inheriting the standard handles.
  (#238)