Fix IDM-1-3 chip-repl example commands (project-chip#31796)

Author: tehampson

src/app/tests/suites/certification/Test_TC_IDM_1_3.yaml

@@ -46,7 +46,7 @@ tests:
           test step can be simulated using chip-repl (when DUT is a commissioner/Client).
           The cluster used in the below command is an example, User can use any supported chip cluster/attribute/command. Note in this example the unique path is created by using 2 different endpoints.
 
-          `await devCtrl.SendBatchCommands(0x12344321, [Clusters.Command.InvokeRequestInfo(1, Clusters.OnOff.Commands.Toggle()), Clusters.Command.InvokeRequestInfo(2, Clusters.OnOff.Commands.Toggle())]`
+          `await devCtrl.SendBatchCommands(0x12344321, [chip.clusters.Command.InvokeRequestInfo(1, chip.clusters.OnOff.Commands.Toggle()), chip.clusters.Command.InvokeRequestInfo(2, chip.clusters.OnOff.Commands.Toggle())])`
 
           On TH(all-clusters-app), Verify that the EndpointIDs, CommandIDs, ClusterIDs in the InvokeRequestMessage (as below) matching with the data sent in the above command
 
@@ -110,7 +110,7 @@ tests:
           test step can be simulated using chip-repl (when DUT is a commissioner/Client).
           The cluster used in the below command is an example, User can use any supported chip cluster/attribute/command. Note in this example the unique path is created by using 2 different endpoints.
 
-          `await devCtrl.SendBatchCommands(0x12344321, [Clusters.Command.InvokeRequestInfo(1, Clusters.OnOff.Commands.Toggle()), Clusters.Command.InvokeRequestInfo(2, Clusters.OnOff.Commands.Toggle())]`
+          `await devCtrl.SendBatchCommands(0x12344321, [chip.clusters.Command.InvokeRequestInfo(1, chip.clusters.OnOff.Commands.Toggle()), chip.clusters.Command.InvokeRequestInfo(2, chip.clusters.OnOff.Commands.Toggle())])`
 
           Verify DUT doesn't crash by seeing next step execute.
       disabled: true
@@ -131,7 +131,7 @@ tests:
           test step can be simulated using chip-repl (when DUT is a commissioner/Client).
           The cluster used in the below command is an example, User can use any supported chip cluster/attribute/command. Note in this example the unique path is created by using 2 different endpoints.
 
-          `await devCtrl.SendBatchCommands(0x12344321, [Clusters.Command.InvokeRequestInfo(1, Clusters.OnOff.Commands.Toggle()), Clusters.Command.InvokeRequestInfo(2, Clusters.OnOff.Commands.Toggle())]`
+          `await devCtrl.SendBatchCommands(0x12344321, [chip.clusters.Command.InvokeRequestInfo(1, chip.clusters.OnOff.Commands.Toggle()), chip.clusters.Command.InvokeRequestInfo(2, chip.clusters.OnOff.Commands.Toggle())])`
 
           Verify DUT doesn't crash by seeing next step execute.
       disabled: true
@@ -152,7 +152,7 @@ tests:
           test step can be simulated using chip-repl (when DUT is a commissioner/Client).
           The cluster used in the below command is an example, User can use any supported chip cluster/attribute/command. Note in this example the unique path is created by using 2 different endpoints.
 
-          `await devCtrl.SendBatchCommands(0x12344321, [Clusters.Command.InvokeRequestInfo(1, Clusters.OnOff.Commands.Toggle()), Clusters.Command.InvokeRequestInfo(2, Clusters.OnOff.Commands.Toggle())]`
+          `await devCtrl.SendBatchCommands(0x12344321, [chip.clusters.Command.InvokeRequestInfo(1, chip.clusters.OnOff.Commands.Toggle()), chip.clusters.Command.InvokeRequestInfo(2, chip.clusters.OnOff.Commands.Toggle())])`
 
           Verify DUT doesn't crash by seeing next step execute.
       disabled: true
@@ -169,7 +169,7 @@ tests:
           test step can be simulated using chip-repl (when DUT is a commissioner/Client).
           The cluster used in the below command is an example, User can use any supported chip cluster/attribute/command. Note in this example the unique path is created by using 2 different endpoints.
 
-          `await devCtrl.SendCommands(0x12344321, 1, Clusters.OnOff.Commands.Toggle())`
+          `await devCtrl.SendCommand(0x12344321, 1, chip.clusters.OnOff.Commands.Toggle())`
 
           On TH(all-clusters-app), Verify that we recieves an InvokeRequestMessage that contains a single InvokeRequests