Fix building ApolloSQLite with Xcode 16b1

[rastersize]

In Xcode 16, or rather Foundation in the iOS 18/etc. SDKs, there’s a new Expression type. The SQLite library also expose this type. This caused an issue compiling the SQLiteDotSwiftDatabase.swift file, as it imports both libraries. This PR disambiguates it for the compiler.

With this change the project once again builds with Xcode 16.

[apollo-cla]

@rastersize: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

[netlify]

👷 Deploy request for apollo-ios-docc pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	ab9247e

[netlify]

👷 Deploy request for eclectic-pie-88a2ba pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	ab9247e

[calvincestari]

Looks like it failed the test__memory_management__givenOperation_withEarlyAndFinalInterceptorChainExit_shouldNotHaveRetainCycle_andShouldNotCrash test which is a known flaky test.

[Mordil]

Do the initializers need to be updated as well since they have explicit references to the types?

[calvincestari]

Do the initializers need to be updated as well since they have explicit references to the types?

I thought that too but then thought that the fully qualified property declaration on line 11 and 12 is enough for the compiler to know which type you actually want to use at those call sites in the initializers. I don't have Xcode 16 yet so I'm guessing at that theory.

[rastersize]

@Mordil @calvincestari They don’t need to be update to build (I tested in Xcode 16b1). I can add it there as well though if you prefer?

[calvincestari]

I can add it there as well though if you prefer?

I don't think it's necessary if the compiler is not complaining about it. There's a chance that it becomes a requirement in a future version of Xcode 16 but if that happens we can add it then.

[calvincestari]

I've confirmed this fix with Xcode 16.0 beta (16A5171c) and skipped the flaky test so we can get this PR merged.

[calvincestari]

I've noticed there are some other build errors with Xcode 16 but they're limited to our test suites which I'll get fixed in a separate PR. This PR alone should be enough to get the dependency building again in your projects. Thanks for the contribution @rastersize.