v8.0.2

release: v8.0.2

Identical code to 8.0.1. Republished because 8.0.1 never became
resolvable.

8.0.1 published successfully by every measure hex offers: the API lists
it, has_docs is true, and the tarball downloads and is a valid hex
archive with the right metadata. But no resolver can see it. A
throwaway project asking for {macula, "8.0.1"} gets "Package not found
in any repo" more than an hour after publication, from a cleared cache
and with the CDN cache-busted.

Specific to this package, not hex being slow: hecate_om 0.10.0,
published three minutes later, resolved normally in the same clean-room
test. So rather than wait on a stuck registry entry with no ETA, this
is the same code under a version that gets a fresh one.

A note on how that was established, because I got it wrong twice first:
grepping hex's compressed per-package blob is not a reliable test. It
reported hecate_om 0.10.0 as absent when a fetch proved otherwise. The
authoritative check is a throwaway project and rebar3 get-deps, which
is what the CHANGELOG entry cites.

Suite 1744 passed 0 failed, elvis clean, ex_doc builds with the same 12
pre-existing warnings.