Integrate closed replicated indices with closed follower indices

[dnhatn]

A spin-off from #33888.

The follower indices do not always have the global checkpoint equals to max_seq_no when closing. Therefore, closing follower indices can make the cluster red. We need to make an alternative sanity check for follower closed indices.

Relates #33888
Relates #38767
Relates #41317

[elasticmachine]

Pinging @elastic/es-distributed

[elasticsearchmachine]

Pinging @elastic/es-distributed (Team:Distributed)

[tlrx]

Quoting Yannick in #38767 (comment):

We need to think how to integrate closed replicated indices with closed follower indices. In the current form, closing follower indices will result in them not being allocated, making the cluster go red. Perhaps instead of requiring max sequence number to be equal to global checkpoint for these shards, which is not guaranteed by the CCR following logic, it would be sufficient to check that max seq number and global checkpoint agree with the primary and require a sync id marker (i.e. perform a synced flush during the VerifyShardBeforeCloseAction) so that peer recovery will be instantaneous.