[#47] [Chore] [Spike] Cache remote Swift packages build-artifacts on CI

[nkhanh44]

• Close #47

What happened 👀

• Speed up the build process when running GitHub actions by using the cache to restore and save the Swift packages build artifacts instead of fetching those dependencies every CI-running trigger.

Insight 📝

• clonedSourcePackagesDirPath flag in scan and build_app - is an xcodebuild build command option specifies the directory to which remote source packages are fetched or expected to be found.

The flow of caching:

1. Restoring cache
2. Build
3. Saving cache

Proof Of Work 📹

Build and Test

Using cache speeds up build up to ~1min.  => [Job with caching](https://github.com/nimblehq/nimble-crypto-ios/actions/runs/3776854252) => [Job without caching](https://github.com/nimblehq/nimble-crypto-ios/actions/runs/3776813587)  => [Job with caching](https://github.com/nimblehq/nimble-crypto-ios/actions/runs/3776490498) => [Job without caching](https://github.com/nimblehq/nimble-crypto-ios/actions/runs/3774802317) Dependencies change when we add a lib (Kingfisher, for example). On [this job](https://github.com/nimblehq/nimble-crypto-ios/actions/runs/3776626724/jobs/6420007037): 

Deploy Firebase

On [this job](https://github.com/nimblehq/nimble-crypto-ios/actions/runs/3778923046/jobs/6423842708): 

[nkhanh44]

@Thieurom Thank you for the helpful feedback 🙏, it's so useful to me. I researched some resources about caching remotely for SPM, but I couldn't find any except for other tools like tuist caching or the tools you mentioned above. For my limited experience and time, I agree that we can use this small speedup improvement, and we will explore a better approach later 😅 .