[fix] [broker] Skip to persist cursor info if it failed by cursor closed

[poorbarcode]

Motivation

We encountered an issue as follows

time	closing topic -> closing curosr	in-progress cursor mark deleting
1	Mark the cursor as closing
2	Persistent cursor metadata into the cursor ledger 54781383
3	Start to close the cursor ledger 54781383
4	Mark the ledger 54781383 is closed in memory
5		Try to write metadata to the ledger 54781383, but the ledger was marked closed
6		Try to write metadata to ZK after failed writing BK
7	Start to write the ledger metadata of 54781383 to ZK
8		The ZK server closed the connection due to the pulsar trying to write a large value
9	Write to ZK failed due to the connection being lost
10		retries and keeps triggering a closing of the ZK connection
11	The retries will fail because the connection is unstable

I think we need at least 3 fixes

• (What this current PR attempts to do) Do not continue executing the in-progress cursor mark deletion after the cursor is closed.
• (I will push another PR to do it) Add a mechanism that limits the data size that will persist with ZK.
• (I will push another PR to do it) Stop retries if such an issue occurs.

Modifications

• Skip to persist cursor info if it failed by cursor closed
• TODO: I will write a test tomorrow.

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository: x