CHASM: Fix standby retention timer generation

[yycptt]

What changed?

• Do not update CloseTime on standby
• Generate retention timer on standby as long as execution is not previously closed.

Why?

• Previous logic won't generate retention timer on standby side if there are state transitions after execution close and those transitions get replicated together with the transition that closes the execution.

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)

[yycptt]

I actually have a xdc retention timer functional test here passing as well.

But today we have a hardcoded minimal retention period and I have to overwrite for the tests to work. So that's not ready for merging yet.

[yycptt]

it's fine to check isStateDirty as well (since state changed to close means the root component state must have changed), but not really necessary, we only need to look at current state and state in db.