[Incremental Builds][Explicit Module Builds] Switch to using incremental dependency scanning

[artemcm]

For Explicit Module Builds, have the driver configure the dependency scanner invocation to serialize its internal scanner cache state after a scan, and attempt to deserialize a prior build's scanner cache state, and validate its contents for an incremental re-scan.

Using functionality implemented in: swiftlang/swift#78962

[nkcsgexi]

@swift-ci please test

[artemcm]

I think this PR will need the compiler change to land in a nightly snapshot first, in order to pass the tests.

[cachemeifyoucan]

I think this PR will need the compiler change to land in a nightly snapshot first, in order to pass the tests.

Shouldn't swift-driver tests work with/without swift compiler changes? It needs to handle both cases otherwise it is going to be a trouble for standalone development.

[artemcm]

@swift-ci test

[artemcm]

Shouldn't swift-driver tests work with/without swift compiler changes? It needs to handle both cases otherwise it is going to be a trouble for standalone development.

We often evolve the driver in-sync with the compiler and make inter-dependent changes between the two. The driver is tested against the current development snapshot compiler, and maintaining test compatibility with much older toolchains would be a large burden here that is not worthwhile, in my opinion. Standalone development works quite well with the same snapshot toolchains as are used in CI here.

[artemcm]

@swift-ci test

[artemcm]

@swift-ci test Windows platform

[cachemeifyoucan]

LGTM function wise.

[artemcm]

@swift-ci test

[artemcm]

@swift-ci test Windows platform

[artemcm]

@swift-ci test Windows platform