exlcude TTL1 trap when set up TTL zero for trap loop

Summary:
Currently AgentVoqSwitchLineRateTest.dramBlocked is failing during warmboot because both TTL_0 and TTL_1 trap are programmed. They correspond to the same underlying sai object programming the same rx reason https://fburl.com/code/nsewyupj, which could lead to conflict or confusion during warmboot when agent attempt to load sai objects and restore switch state.

This diff resolves this issue by excluding TTL1 trap when calling setTTLZeroCpuConfig()

Reviewed By: jasmeetbagga

Differential Revision:
D68798218

Privacy Context Container: L1125642

fbshipit-source-id: 557310efc9d7bee273f4ad7b2cb78e4c426a2251

fboss/agent/test/utils/CoppTestUtils.cpp

@@ -685,7 +685,7 @@ void setTTLZeroCpuConfig(
     // don't configure if not supported
     return;
   }
-
+  excludeTTL1TrapConfig(config);
   std::vector<cfg::PacketRxReasonToQueue> rxReasons;
   bool addTtlRxReason = true;
   if (config.cpuTrafficPolicy().has_value() &&