feat(ci): add caching for CMake FetchContent in CI workflow

[jihuayu]

Due to the current instability of GitHub services, dependency download failures occur frequently during CI runs. I add FetchContent caching to prevent these network issues from failing the CI.

[PragmaTwice]

You can use DEPS_FETCH_DIR instead of caching these _deps directories (which may bring some chaos).

[jihuayu]

@PragmaTwice Thanks for the reminder. I’ve made the changes.
Do you think it’s better to cache each job individually (now), or do a full cache at the beginning of the action?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[PragmaTwice]

env.CMAKE_JEMALLOC_VARIANT, env.CMAKE_LUA_VARIANT,

I don't think we need this. They are useless and introduce complexity.

Do you think it’s better to cache each job individually (now), or do a full cache at the beginning of the action?

I think we'd better to choose the simplest way.

[jihuayu]

env.CMAKE_JEMALLOC_VARIANT, env.CMAKE_LUA_VARIANT,
I don't think we need this. They are useless and introduce complexity.

This variable is just for readability; otherwise, we’d be stuck facing a very long cache key.
${{ format('cmake-fetch-archives-v1-{0}-{1}-{2}-{3}', matrix.os, startsWith(matrix.os, 'macos') && 'without-jemalloc' || matrix.without_jemalloc && 'without-jemalloc' || 'with-jemalloc' , matrix.without_luajit && 'without-luajit' || 'with-luajit' , hashFiles('CMakeLists.txt', 'cmake/**/*')) }}

As I understand it, the Lua and jemalloc options must be cached separately because they pull different source codes. Is that correct?

[PragmaTwice]

As I understand it, the Lua and jemalloc options must be cached separately because they pull different source codes. Is that correct?

Nope. The dep dir can be shared. The filename is different for different deps.