Add FIPS 202 SHA3-256 reporting

[JoeJingzhou]

Closes #2

Summary

• add standards-compliant SHA3-256 (FIPS 202) hashing to the evidence table
• include SHA3-256 in CSV, real XLSX, hash PDF, Word, and email forensic PDF exports
• add a bounded on-page System Console with calculation and export status
• cache calculated digests and handle file read/hash failures without stalling the queue
• pin new browser dependencies with SHA-384 integrity checks

FIPS 202 correctness

CryptoJS 4.1.1 SHA3 uses legacy Keccak padding and does not produce the NIST FIPS 202 digest requested by the issue. This uses js-sha3 for SHA3-256 while retaining CryptoJS for MD5 and SHA-256. For abc, the page produces 3a985da74fe225b2045c172d6bd390bd855f086e3e9d525b46bfe24511431532.

Verification

• inline script syntax check
• headless Chrome upload test with abc.txt
• MD5, SHA-256, and SHA3-256 checked against known vectors
• CSV and XLSX contents checked for the SHA3-256 value
• CSV, XLSX, PDF, and DOCX downloads generated and verified by file signatures

/claim #2

[JoeJingzhou]

/claim #2