v0.6.0

Upgrade step: the hub commands of 0.5.0 and older refuse an export with the new formats, so upgrade
codemeta-drift with the file. A consumer that vendors the mapping schema vendors the 1.6 schema and
mapping-vectors.json with it, and runs the vectors through its resolver: a 1.6 export fails the 1.4 schema that 0.5.0 shipped.

Added

• The mapping export covers 22 more formats: DataCite, setup.py, Ruby gemspecs, Maven's pom.xml, CPAN's
  META.json, NuGet's .nuspec, Dart's pubspec.yaml, Cabal, typst.toml, Quarto's _extension.yml, the GitHub
  API, Figshare, bio.tools, Leiningen's project.clj, Octave's DESCRIPTION, publiccode.yml 0.8, swMATH, SPDX 2.3,
  CodeMeta 2.0, DCAT 3, DOAP and Wikidata, and the coverage page and SSSOM spokes cover them too. Each row was
  checked against the format's own tools and spec. See the mapping export.
• Ship mapping-vectors.json beside the mapping schema: test cases of path, document and the values the path
  resolves to, for a consumer to run through its own resolver. See the mapping export.

Changed

• The BibTeX codeRepository row reads repository | url, since plain BibTeX styles print only url.
  See the coverage page.
• Schema 1.6 extends the path grammar: a + b reads both parts, [k=v] also matches a list that holds v, and
  a key may carry a prefix. The PKG-INFO author rows use +, the Project-URL rows end in .url, and the DCAT 3
  and DOAP rows use prefixed names such as dcterms:title. See the
  path grammar.

Fixed

• A person sub-term such as author.@id is read from the alternative its term resolved through, not by first
  match, so one person's ORCID never lands on another. See the mapping export.
• The schema watcher now also opens a citesync issue when a hash in MAPPING_SOURCE differs from the file published at the pinned tag, and its run prints a notice when it skips publishing for lack of a token. The docs name the token permissions it needs.