Unify and move receive timestamp config

Summary: We shouldn't have config in the codec types. Instead solve the plumbing problem more explicitly, and only define the config in one place.

Reviewed By: jbeshay

Differential Revision: D45881730

fbshipit-source-id: fab6c967a38172f16e57a8978b10460fd196902e

third-party/proxygen/src/proxygen/httpserver/samples/hq/HQCommandLine.cpp

@@ -276,9 +276,8 @@ void initializeTransportSettings(HQToolParams& hqUberParams) {
 
   if (FLAGS_use_ack_receive_timestamps) {
     hqParams.transportSettings.maybeAckReceiveTimestampsConfigSentToPeer.assign(
-        {.max_receive_timestamps_per_ack =
-             FLAGS_max_ack_receive_timestamps_to_send,
-         .receive_timestamps_exponent = kDefaultReceiveTimestampsExponent});
+        {.maxReceiveTimestampsPerAck = FLAGS_max_ack_receive_timestamps_to_send,
+         .receiveTimestampsExponent = kDefaultReceiveTimestampsExponent});
   }
 } // initializeTransportSettings