Fixes #20414

Master Issue: ##20414

Motivation

#17221 describes an environment when multiple bookie copies are corrupted, or a Ledger has been deleted. The loss of schema ledger results in new producers and consumers not even being created and working properly.

So we need a solution that does not just skip the schema with the missing ledger, but actually supplements the broken schema ledger.

Modifications

Add a new method tryCompleteTheLostSchema() in SchemaStorage and SchemaRegistry

CompletableFuture<Long> tryCompleteTheLostSchemaLedger(String key, SchemaVersion version, SchemaData schema);

1. get schemalocator from metastore
2. Create a new ledger. And write SchemaStorageFormat.SchemaEntry built with schemaData and schemaVersion.
3. update schemalocator to metastore(new ledger id)

Verifying this change

• Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

• Added integration tests for end-to-end deployment with large payloads (10MB)
• Extended integration test for recovery after broker failure

Documentation

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

Matching PR in forked repository

PR in forked repository: Denovo1998#4