Sync the GitHub runner clock with the Windows time server

[bjornoleh]

Adding a step to workflow jobs that interface Apple servers, as a workaround for build issues caused by runner clocks being out of sync. See https://github.com/actions/runner issue number 2996 for details.

• name: Sync clock
  run: sudo sntp -sS time.windows.com

Added to the following workflows / jobs:

• validate_secrets.yml / validate-fastlane-secrets
• add_identifiers.yml / identifiers
• build_iAPS.yml / build
• create_certs.yml / certificates

[bjornoleh]

All four workflows have been tested successfully. No relevant errors were encountered.

The Sync clock step runs this command:

run: sudo sntp -sS time.windows.com

Observed time differences before syncing the clock:
Validate Secrets: +0.369539 +/- 0.060284
Add Identifiers: -4.125202 +/- 0.041137
Create Certificates: +0.236225 +/- 0.054157
Build iAPS: +0.128533 +/- 0.065851

Some more runs

-215.021491
+0.083260
+ 0.104221
+ 0.101976
+ 0.158417

[bjornoleh]

@Jon-b-m , this PR is ready to be merged. You may also want to get this into #400, so that users of main can get rid of all the build errors.

If the root cause in the github runners (macos-13) gets fixed, we can opt to revert this workaround. But it does no harm.

[dnzxy]

@Jon-b-m , this PR is ready to be merged. You may also want to get this into #400, so that users of main can get rid of all the build errors.

Please watch out not to immediately port auto builds with this fix if we do not want to push auto build to main yet.

[Jon-b-m]

@Jon-b-m , this PR is ready to be merged. You may also want to get this into #400, so that users of main can get rid of all the build errors.

If the root cause in the github runners (macos-13) gets fixed, we can opt to revert this workaround. But it does no harm.

It would be better if you PR:ed this particular fix to the 2.3.0 PR, if needed, thanks.

[bjornoleh]

@Jon-b-m , this PR is ready to be merged. You may also want to get this into #400, so that users of main can get rid of all the build errors.
If the root cause in the github runners (macos-13) gets fixed, we can opt to revert this workaround. But it does no harm.

It would be better if you PR:ed this particular fix to the 2.3.0 PR, if needed, thanks.

Thanks, I have opened #406 to get this into 2.3.0.