[doc] fix the FORWARD_TRANSITIVE compatibility check logic.

[yangl]

Motivation

FORWARD_TRANSITIVE | Can read the last schema --> Can read all schemas

Compatibility check strategy	Check logic
ALWAYS_COMPATIBLE	All pass
ALWAYS_INCOMPATIBLE	No pass
BACKWARD	Can read the last schema
BACKWARD_TRANSITIVE	Can read all schemas
FORWARD	Can read the last schema
FORWARD_TRANSITIVE	Can read the last schema --> Can read all schemas
FULL	Can read the last schema
FULL_TRANSITIVE	Can read all schemas

Modifications

update the FORWARD_TRANSITIVE check logic to Can read all schemas

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

Does this pull request potentially affect one of the following parts:

If yes was chosen, please highlight the changes

• Dependencies (does it add or upgrade a dependency): (yes / no)
• The public API: (yes / no)
• The schema: (yes / no / don't know)
• The default values of configurations: (yes / no)
• The wire protocol: (yes / no)
• The rest endpoints: (yes / no)
• The admin cli options: (yes / no)
• Anything that affects deployment: (yes / no / don't know)

Documentation

Check the box below or label this PR directly.

Need to update docs?

• doc-required
  (Your PR needs to update docs and you will update later)

• no-need-doc
  (Please explain why)

• doc
  (Your PR contains doc changes)

• doc-added
  (Docs have been already added)

[Anonymitaet]

@congbobo184 can you review this PR from the technical perspective?

[codelipenghui]

The check logic is for a new schema, for FORWARD_TRANSITIVE compatibility, the new schema should be able to read the data from the last schema and should be able to be read by all the existing schema.

@congbobo184 Please help confirm

[congbobo184]

if schema is FORWARD_TRANSITIVE, consumer only can read the last schema, because in FORWARD_TRANSITIVE, we need to upgrade producer first, so in FORWARD_TRANSITIVE, we only check can read the last schem is enough.
@yangl