Add swift-asn1 and swift-certificates to update-checkout

[neonichu]

These are needed for SwiftPM registry work. We're using the main branch for now but will switch to concrete versions closer to the release.

[neonichu]

@swift-ci please test

[neonichu]

@swift-ci please smoke test

[shahmishal]

Useful info https://github.com/apple/swift/blob/main/docs/Branches.md?plain=1#L91

[neonichu]

apple/swift-crypto#149
apple/swift-certificates#32
swiftlang/swift-package-manager#6216
@swift-ci please smoke test

[neonichu]

apple/swift-crypto#149
apple/swift-certificates#32
swiftlang/swift-package-manager#6216
@swift-ci please test

[neonichu]

apple/swift-crypto#149
swiftlang/swift-package-manager#6216
@swift-ci please test

[neonichu]

swiftlang/swift-package-manager#6216
@swift-ci please test

[neonichu]

swiftlang/swift-package-manager#6216
@swift-ci please smoke test

[neonichu]

Some random Swift tests failed on the macOS job

Failed Tests (2):
  Swift(iphonesimulator-x86_64) :: diagnostics/pretty-printed-diagnostics.swift
  Swift(iphonesimulator-x86_64) :: diagnostics/pretty-printed-source-loc-directive-diags.swift

This also means we did not even get to building SwiftPM. The Linux job passed and build the new libraries as expected.

[neonichu]

swiftlang/swift-package-manager#6216
@swift-ci please test macOS

[finagolfin]

@neonichu, just noticed this when building the latest trunk snapshot from source: do you plan on switching to concrete versions before the 5.9 branch? Because these repos don't have any snapshot tagging set up yet and will just check out random commits from the main branch until then.

That's fine for toolchain developers who just build latest trunk, but causes problems for those who want more stable builds and use the snapshot tags for that.

[neonichu]

@buttaface yah, the plan is to switch to a concrete version, like we do for e.g. swift-crypto, once the libraries are mature enough (sometime before the 5.9 branch date).

[yim-lee]

pinning them in #64285