Pull in chacha20 0.10.2 and drop the temporary deny.toml exception

[henry40408]

Follow-up to #100.

chacha20 0.10.0 and 0.10.1 were yanked upstream. The graph reaches 0.10.0 transitively via rand -> sqlx-postgres -> sqlx, which turned the deny job red on main.

The unyanked 0.10.2 was published 2026-08-27, so it only clears the 7-day publish cooldown on 2026-09-03. #100 therefore parks a temporary [advisories] ignore entry in deny.toml rather than updating the lockfile.

To do, from 2026-09-03

• cargo update -p chacha20 (expect 0.10.0 -> 0.10.2)
• Remove the chacha20@0.10.0 entry from [advisories] ignore in deny.toml, along with its comment
• Revert the ignore doc comment above it if the list ends up empty again
• cargo deny check to confirm advisories pass without the exception

A yank is not a security advisory, so there is no urgency beyond keeping CI honest.

🤖 Generated with Claude Code