v1.1.1

Lucida v1.1.1 — `lucida update` keeps a cargo install where cargo put it

Three fixes above v1.1.0, all in how `lucida update` treats a copy that
cargo installed.

  fix   a copy installed from crates.io is updated from crates.io. It was
        rebuilt from git, which worked and quietly turned it into a git
        install. The source is read from cargo's own install record.
  fix   the reinstall goes into the copy's own cargo home. It went
        wherever cargo was configured to install today, so a changed
        CARGO_INSTALL_ROOT or install.root could leave the copy on PATH
        old while reporting success.
  fix   a cargo home behind a symlink, and Windows' canonical paths, are
        recognised, so such a copy is no longer overwritten as though it
        were a download.

The first release whose crate the release workflow is set to publish to
crates.io, by trusted publishing, from the same commit as the binaries.