Please describe the problem you are trying to solve.

Currently in #2070, remeshing is allowed only at the beginning of completed time-window and the time window needs to be finished after remeshing.

This prevents any subcyling if the solver wants to remesh.

Describe the solution you propose.

Add support for remeshing after subcycling, which requires maintaining the information that the coupling scheme is in the first iteration of a time window.

Add support for subcycling after remeshing, which requires maintaining the meshLock state until the end of the time window in order to trigger the reinitialization.

Describe alternatives you've considered

Keep the current restriction.

Additional context

#2070
Related to #2093