Refine PR test job name (sonic-net#17249)

What is the motivation for this PR?
Baseline test will use test plan name to distinguish different test platforms, and test plan name determined by pipeline job name, so job name should have a unified standard and be easy to distinguish.

How did you do it?
Replace _ in job name with - to make it easier to distinguish different test jobs, for example, in baseline test, once we create multiple test plans for t0, the test plan name will be xxx_impacted-area-kvmtest-t0_number, difficult to distinguish with t0_2vlans test job xxx_impacted-area-kvmtest-t0_2vlans_number when we want to search t0 tests, so use - in job name.
Use t0-sonic not sonic-t0, because in all other places, we are using t0-sonic.
Change multi-asic to multi-asic-t1 to show the topo type.

Co-authored-by: xwjiang2021 <96218837+xwjiang2021@users.noreply.github.com>

Author: xwjiang-ms

azure-pipelines.yml

@@ -132,7 +132,7 @@ stages:
           MGMT_BRANCH: "master"
 
   - job: impacted_area_t0_2vlans_elastictest
-    displayName: "impacted-area-kvmtest-t0_2vlans by Elastictest"
+    displayName: "impacted-area-kvmtest-t0-2vlans by Elastictest"
     dependsOn:
     - get_impacted_area
     - choose_between_mixed_and_py3_ptf_image
@@ -222,7 +222,7 @@ stages:
           MGMT_BRANCH: "master"
 
   - job: impacted_area_multi_asic_elastictest
-    displayName: "impacted-area-kvmtest-multi_asic by Elastictest"
+    displayName: "impacted-area-kvmtest-multi-asic-t1 by Elastictest"
     dependsOn:
     - get_impacted_area
     - choose_between_mixed_and_py3_ptf_image
@@ -250,8 +250,8 @@ stages:
           KVM_IMAGE_BRANCH: $(BUILD_BRANCH)
           MGMT_BRANCH: "master"
 
-  - job: impacted_area_sonic_t0_elastictest
-    displayName: "impacted-area-kvmtest-sonic_t0 by Elastictest"
+  - job: impacted_area_t0_sonic_elastictest
+    displayName: "impacted-area-kvmtest-t0-sonic by Elastictest"
     dependsOn:
     - get_impacted_area
     - choose_between_mixed_and_py3_ptf_image
@@ -311,7 +311,7 @@ stages:
 
   # This PR checker aims to run all t1 test scripts on multi-asic topology.
   - job: impacted_area_multi_asic_t1_elastictest
-    displayName: "impacted-area-kvmtest-multi_asic_t1 by Elastictest - optional"
+    displayName: "impacted-area-kvmtest-multi-asic-t1 by Elastictest - optional"
     dependsOn:
     - get_impacted_area
     - choose_between_mixed_and_py3_ptf_image