Option to delete a checkpoint after resumption

In use-cases where a 'expire at' property cannot be determined when creating a checkpoint, we need abilities to manual trigger deletion. However, in certain cases the checkpointID maybe random or hard to keep track of, making manual deletion using checkpointID costly. An option to delete a checkpoint after resumption will help

Start by tracing the checkpoint creation, resumption, and deletion entry points in the Go codebase, since the issue names no files or tests. Determine how a checkpoint can be identified after resumption, then add an option for deletion at that point and verify that resumed checkpoints are removed without requiring the caller to retain the checkpoint ID.

Written by the indexing model from the issue text.