docs: remove CHANGELOG-archive.md; history lives in tags and releases

[dimitri-yatsenko]

Summary

Removes CHANGELOG-archive.md. The release history it preserved (0.3.2 through 0.14.3) now lives entirely in git tags and GitHub Releases, which is where its own header already pointed.

Backfill done before this PR

Tags and releases were filled in so that nothing in the archive is lost:

• 19 new tags for versions the archive or PyPI listed but git did not: 0.3.2–0.3.9, 0.4.1–0.4.3, 0.4.5–0.4.10, 0.5.0, 0.11.2. Each sits on the first master merge whose __version__ equals the tag, the rule the existing tags follow. For 0.4.8, 0.4.9, 0.4.10, and 0.5.0, the PyPI sdists match those commits file for file.
• 22 new releases carrying the archived notes verbatim: every new tag except 0.4.8, which has no archive entry, plus the existing tags v0.8.0, v0.9.0, v0.10.0, and v0.11.3. All were created with --latest=false; v2.3.4 remains Latest.
• v0.10.1: its release body was empty and now has the archived notes.

Two judgment calls:

• 0.4.1–0.4.3: the archive cites PRs Fix handling of long error messages in job table #266, improved table appearance in jupyter #267, and Fixed issues #268 and #270, removed support of Views. #271, but those merges set __version__ to 0.4.2, 0.4.3, and 0.4.4. The tags follow the version strings.
• 0.11.2: PyPI's 0.11.2 (2019-04-13) was built from f41d474 with an uncommitted version bump, so v0.11.2 points there. The archive's later 0.11.2 entry (the pyparsing fix, Jul 25, 2019) shipped as 0.11.3; the v0.11.2 release notes say so.

PyPI pre-releases without tags (0.8.0rc0, 0.12.dev1–dev3) were left untagged.

Test plan

• Every version heading in the archive has a tag and a GitHub release whose body contains its archived notes. Items in existing 0.11.1–0.13.7 releases are worded differently but match.
• No other file references CHANGELOG-archive.md.
• Creating releases on the old tags triggered no workflow runs, because the publish workflow does not exist at those commits.