[mayokunyusuf]

When JobScheduler stops an expedited job running HeapAnalyzerWorker (e.g. on Android 12–16 after timeout or doze), WorkManager reschedules the work while the current doWork() continues running. Because HeapAnalyzerWorker was not checking isStopped or passing a CancelSignal, multiple full heap analyses could run concurrently in the same process, often ending in OutOfMemory.

This mirrors the pattern already used in RemoteHeapAnalyzerWorker:

• Pass CancelSignal to runAnalysisBlocking checking isStopped
• Catch CanceledException, log the cancellation, and return Result.retry()
• Do not send HeapAnalysisDone or progress events when stopped

Closes #3019.