Using Activity isolation as a security boundary

This post details how keeping PII scan, classification, and storage within a single Activity enforces a security boundary, preventing raw PII from crossing Activity boundaries or appearing in the Temporal UI. It also covers using heartbeating for long-running streaming Activities to detect stuck workers and resume processing from the last checkpoint, and employing a DataStore contract for swappable storage implementations.