[Scheduler] Always attempt DeleteSchedule on both stacks

[lina-temporal]

What changed?

• Delete is now called for both CHASM/V1 stacks, as long as CHASM is enabled, regardless of success/error from CHASM stack.

Why?

• CHASM block successfully deleting means that the V1 handler never gets a chance to run, blocking V1 deletes after a schedule has gone from V1->V2->V1 (rollback).

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)

[chaptersix]

Additionally could you add a check for closed and return a not found from the chasm delete schedule handler?

[chaptersix]

Additionally could you add a check for closed and return a not found from the chasm delete schedule handler?

the frontend request is not guaranteed execute to completion.