- Removed the `util.HasCurrentStateBeenReported(pod)` check and now just simply ignore all terminal pods
   - Other processes handle terminal pods - leave it to them to handle
   - Having `util.HasCurrentStateBeenReported(pod)` just added a race between detecting issues / reporting state
 - Made it so we don't handle pods stuck in terminal state IF the executor was the one that called delete
   - Cluster context will handle this issue itself as it was the one to call delete, so leave it to that to handle
   - Making the issue handle tell the cluster context about this potential issue
     - This is so if the executor restarts, the pod being stuck will still get handled
     - We don't need to send events about it, as the executor already was trying to delete it

Signed-off-by: JamesMurkin <jamesmurkin@hotmail.com>