backupCodec makes it meaningless to set serialization protocols on the server side #2875
Description
This PR introduces the backupCodec field in the triple protocol, with the goal of allowing the server to use the client's serialization protocol for parsing when the serialization protocols on the server and client sides do not match, thus enhancing the availability of the triple server.
However, this makes the option to set the serialization protocol on the server side meaningless.
We should consider whether to remove the option for the server's serialization protocol or to remove backupCodec.
If we decide to keep backupCodec, it deserves a better name.