Is your feature request related to a problem? Please describe.
For class forward/backward compatibility, fury needs to send class meta to peer everytime, which is time-consuming, and consume more bandwidth.

Describe the solution you'd like
If the serialization sender and receiver are serialized serially in a certain context (TCP connection), then some metadata (class name, field name, final field type information, etc.) can be shared between multiple requests in that context. These type information will be sent to the other end during the first serialization in that context. This way, the other end can rebuild the same deserializer based on the type information, so that it can still deserialize correctly when the fields on the serialization and deserialization sides are inconsistent. At the same time, unnecessary metadata serialization overhead can be reduced in subsequent serialization.

Additional context
#197