CHASM: Use force deletion for chasm execution in namespace deletion

[yycptt]

What changed?

• Use force deletion for chasm execution in namespace deletion
• Add functional test for forcing deleting chasm executions
• We have log for force deletion as well

Why?

• DeleteWorkflowExecution API is an async graceful deletion api that only works for Workflow, but not other CHASM archetypes.
• Upon namespace deletion we need to delete chasm executions as well and we can use force deletion to do it.

How did you test it?

• built
• run locally and tested manually
• covered by existing tests
• added new unit test(s)
• added new functional test(s)

[yiminc]

this is only used for namespace deletion? if true, then we should just use force delete here.

[yycptt]

We will need to refactor force deletion api handle a bit though. Today it only does best effort deletion on history events, we will need a non best effort mode first and then switch to it.