ci: apple & android targets for CI matrix

[itsezc]

Closes #368

Minor change to the CI matrix to ensure SurrealKV builds for Apple (iOS, watchOS, tvOS, visionOS) & Android platforms

[arriqaaq]

Thank you @itsezc

[itsezc]

@arriqaaq looks like we have to move to nightly builds for Rust as some of these platforms are tier 3 in rust, is this something you're open to?

I've tested SurrealKV built locally on tvOS and watchOS and it builds but not able to run as theres inadequate resources. We can remove tvos and watchos targets, and add them back in later if the plan is to support them.
visionos is a different story, it's still classified as Tier 3 and I'd love to be able to ship an embedded version of SurrealDB + SurrealKV into it, but we'll still need to build with rust nightly.

[arriqaaq]

Hey @itsezc

Firstly, thank you for the suggestion.

My thoughts are that the main CI pipeline should reflect the platforms we officially support and guarantee to build on stable Rust.

If some of the newer Apple targets (for example visionOS) are currently Tier 3 in Rust, how about we not make nightly Rust or experimental targets a requirement for all contributors?

Can we instead:

• Keep the main CI job on stable Rust
• Limit it to platforms that build reliably on stable
• Add a separate experimental job for other targets (visionOS, etc) that runs on nightly
• Mark that job as non-blocking so it doesn’t fail PRs?

This way:

• Stable Rust remains our baseline
• Contributors aren’t forced onto nightly
• Experimental breakage won’t block unrelated work

Let me know your thoughts

[itsezc]

Hi, that makes alot of sense and keeps contributors happy too!

[itsezc]

@arriqaaq theres a few target OS that aren't handled in one of the dependencies (fs2), I'd like to patch this via vendoring on Cargo, does this work for you?

The crate hasn't been updated in what seems to be for 9 years, so contributing is a bit out of reach, hence my suggestion.

[arriqaaq]

Hey @itsezc

Sorry for the delayed response. Please feel free to make changes in the PR, will have a look and will discuss with you and we can look into getting it merged