Skip warm-reboot part in qos/test_qos_dscp_mapping.py for dualtor topologies (sonic-net#21820)

What is the motivation for this PR?
This test triggers warm reboot which is broken on dualtor and can cause orchagent crash etc.

How did you do it?
Skipping the warm-reboot part of the test for dualtor

How did you verify/test it?
ran the test

Signed-off-by: mssonicbld <sonicbld@microsoft.com>

Author: rajkumar1-arista

tests/qos/test_qos_dscp_mapping.py

@@ -493,8 +493,14 @@ def test_dscp_to_queue_mapping(self, ptfadapter, rand_selected_dut, localhost, d
         with allure.step("Run test"):
             self._run_test(ptfadapter, duthost, tbinfo, test_params, inner_dst_ip_list, dut_qos_maps_module, dscp_mode)
 
-        if completeness_level != "basic" and \
-                not duthost.dut_basic_facts()['ansible_facts']['dut_basic_facts'].get("is_smartswitch"):
+        is_smartswitch = duthost.dut_basic_facts()['ansible_facts']['dut_basic_facts'].get("is_smartswitch", False)
+        topo_name = tbinfo["topo"]["name"]
+        if (
+            completeness_level != "basic"
+            and not is_smartswitch
+            and "dualtor" not in topo_name
+            and "t1" not in topo_name
+        ):
             with allure.step("Do warm-reboot"):
                 reboot(duthost, localhost, reboot_type="warm", safe_reboot=True, check_intf_up_ports=True,
                        wait_warmboot_finalizer=True)