refactor(rpc): refactor request meta to adapt to new version of rpc protocol

[levy5307]

Refactor our thrift message parser by redesigning the request header format, to support adding is_backup_request new field.

Side effect:
This pull request will import incompatibility.

old/new client --> new server ok.
old client --> old server is ok, too.
but new client --> old server is not ok.
Because the connection will be disconnected by server. So we can`t get any information about version incompatibility, it simply disconnects the connection.

[neverchanje]

These fields should be defined optional, be consistent with what server-side defines.

Actually I suggest just copy the thrift codes from pegasus.

// Metadata field of the request in rDSN's thrift protocol (version 1).                                                                                                                                   
// TODO(wutao1): add design doc of the thrift protocol.                                                                                                                                                   
struct thrift_request_meta_v1                                                                                                                                                                             
{                                                                                                                                                                                                         
    // The replica's gpid.                                                                                                                                                                                
    1:optional i32 app_id;                                                                                                                                                                                
    2:optional i32 partition_index;                                                                                                                                                                       
                                                                                                                                                                                                          
    // The timeout of this request that's set on client side.                                                                                                                                             
    3:optional i32 client_timeout;                                                                                                                                                                        
                                                                                                                                                                                                          
    // The hash value calculated from the hash key.                                                                                                                                                       
    4:optional i64 client_partition_hash;                                                                                                                                                                 
                                                                                                                                                                                                          
    // Whether it is a backup request. If true, this request (only if it's a read) can be handled by                                                                                                      
    // a secondary replica, which does not guarantee strong consistency.                                                                                                                                  
    5:optional bool is_backup_request;                                                                                                                                                                    
} 

[levy5307]

I don`t suggest to use optional in java client. We use optional in pegasus server because we want it to have good compatibility, so we can delete these data in later version of java client. But in this version, these data is a must.

it‘s misjudgments