Test Schedules: Need to specify all branches in yaml (Azure#5425)

According to the docs we actually need to specify all branches in the yaml.
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/scheduled-triggers?view=azure-devops&tabs=yaml

builds/e2e/connectivity.yaml

@@ -5,11 +5,17 @@ pr: none
 # Don't run any scheduled tests on Sunday, as release/1.1 runs its scheduled tests then.
 schedules:
 - cron: "0 0 * * 1,2,3,4,5,6"
-  displayName: Daily midnight build
+  displayName: Daily build master
   branches:
     include:
     - master
   always: true
+- cron: "0 12 * * 1,2,3,4,5,6"
+  displayName: Daily build release/1.2
+  branches:
+    include:
+    - release/1.2
+  always: true
 
 variables:
   NugetSecurityAnalysisWarningLevel: warn

builds/e2e/nested-connectivity.yaml

@@ -8,11 +8,17 @@ pr: none
 # Test schedule the same between master and release/1.2, but offset 12 hours. 
 schedules:
 - cron: "0 0 * * *"
-  displayName: Daily midnight build
+  displayName: Daily build master
   branches:
     include:
     - master
   always: true
+- cron: "0 12 * * *"
+  displayName: Daily build release/1.2
+  branches:
+    include:
+    - release/1.2
+  always: true
 
 variables:
   NugetSecurityAnalysisWarningLevel: warn

builds/e2e/nested-e2e.yaml

@@ -8,11 +8,17 @@ pr: none
 # Test schedule the same between master and release/1.2, but offset 12 hours. 
 schedules:
 - cron: "0 6 * * *"
-  displayName: Daily morning build
+  displayName: Daily build master
   branches:
     include:
     - master
   always: true
+- cron: "0 18 * * *"
+  displayName: Daily build release/1.2
+  branches:
+    include:
+    - release/1.2
+  always: true
 
 variables:
   # A 'minimal' pipeline only runs one end-to-end test (TempSensor). This is useful for platforms or