Update scheduled triggers in pipelines

[damonbarry]

This change makes several updates to schedule triggers in various pipelines to bring them up to date and make them more consistent with one another:

• Update triggers to target release/1.3 instead of release/1.2. Note that, given how schedule triggers work in Azure pipelines, these changes in main won't actually impact the schedules in release/1.2 or release/1.3. To do that, we'll need to make changes in the respective branches. Disabled scheduled autorun for test pipelines #6453 covers release/1.2, and I'll merge this change into release/1.3 as well.
• In cases where schedule triggers are found in other branches besides main for a given pipeline, bring those changes into main for consistency. Again, this doesn't actually change how the schedule triggers will work, it simply brings all the information together into one place.
• In nested-e2e.yaml, restore time offsets to "0 0 ..." and "0 12 ..." for consistency with other pipelines, since it no longer shares test agents with the recently removed nested connectivity pipeline.
• In upgrade-scenarios.yaml, fix a problem where the schedule trigger was only firing for main. We want it to fire for the release branches as well.
• In service-deployment.yaml, update the schedule trigger to be consistent with how it's defined in release/1.1.
• Remove trailing whitespace as needed.

Azure IoT Edge PR checklist:

This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines and Best Practices

• I have read the contribution guidelines.
• Title of the pull request is clear and informative.
• Description of the pull request includes a concise summary of the enhancement or bug fix.

Testing Guidelines

• Pull request includes test coverage for the included changes.
• Description of the pull request includes
  • concise summary of tests added/modified
  • local testing done.

[nlcamp]

I guess this nested longhaul pipeline doesn't share the same agents as the single-node longhaul, so it's ok to use the same schedule?

[damonbarry]

That's correct. This is the schedule we're already using today, I just copied it to the main branch as well.

[nlcamp]

Looks good to me.

This reminded me of another change we'll need to make when we create the release/1.3 branch. I've created a PBI to address it titled "Change 'main' to 'release/1.3' in upgrade scenarios pipeline on release/1.1 branch"