Seata multi-version protocol control

## Why you need it?
Is your feature request related to a problem? Please describe in details
https://github.com/seata/seata/discussions/5628%EF%BC%89

1: seata communication protocol message structure in the 0.7.1 version of the more significant changes, but did not do the previous protocol compatibility process, resulting in the old version of the server side of the user if you want to upgrade can only be upgraded at the same time as the server and the client, that is, either to put up with a period of time can not be communicated with, or downtime upgrades.
2: protocol scalability problems, the expansion of fields or types are not compatible with the previous protocol. (The extension method is not uniform, the adaptation logic will be scattered in various layers, resulting in confusion and unmanageability.)

Past discussions: https://github.com/seata/seata/pull/4569/files

## How it could be?
A clear and concise description of what you want to happen. You can explain more about input of the feature, and output of it.

## Other related information
Add any other context or screenshots about the feature request here.

Start by reading discussion #5628 and the changes in PR #4569, then trace the 0.7.1 protocol message changes described in the issue. The issue names no files or tests; done means an agreed, implementable approach for multi-version compatibility and protocol extensibility.

Written by the indexing model from the issue text.