[SAI PTF]Support sai ptf v2 Syncd-rpc

[richardyu-ms]

Why I did it

Make a new syncd rpc container which can use the new sai-ptf structure. The new sai-ptf structure will generate RPC APIs from SAI interface directly.

In order to get that new syncd-rpc container, there are some problem need to handle

• Cause the new SAI-PTF will generate RPC API automatically, it will not compatiable with the previous approach that has been used in existing syncd-rpc, then we need a new version of syncd-rpc.
  The previous RPC APIs are generate from here https://github.com/opencomputeproject/SAI/blob/master/test/saithrift/Makefile
  The new RPC APIs are generated by this https://github.com/opencomputeproject/SAI/blob/master/test/saithriftv2/Makefile
  Cause there are some cases still need the exisitng RPC APIs, then we need to use differernt versions of rpc API set for different test purpose.
• Current syncd-rpc use thrift 0.11.0, but new sai-ptf structure use thrift 0.14.1, we need use a new verson of thrift

How I did it

for the pronlems above, in this PR, the solutions are:

• for different RPC structure, use two different version of syncd-rpc, the version will be set base on which rpc build structure will be used with build process SAITHRIFT_V2
• for 0.11.0 and 0.14.1, use the same parameter SAITHRIFT_V2 to use different thrift version when build

How to verify it

Test done:
#12619
#12762
#12766
NOSTRETCH=y NOJESSIE=y make configure PLATFORM=broadcom NOSTRETCH=y NOJESSIE=y ENABLE_SYNCD_RPC=y make target/docker-syncd-brcm-rpc.gz NOSTRETCH=y NOJESSIE=y ENABLE_SYNCD_RPC=y make target/docker-saiserver-brcm.gz

Signed-off-by: richardyu-ms [email protected]

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205

Description for the changelog

Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)

[richardyu-ms]

regarding to the problem to compatiable with thrift 014, after consideration, will upgrade existing thrift 11 to 14 at first, then we can make other component get the benefit from this change, mean while avoid to use different version of packages.