fix: revert dependency versions to resolve C++ toolchain failures

- platforms: 1.0.0 → 0.0.11
- rules_cc: 0.2.0 → 0.1.1
- bazel_skylib: 1.8.1 → 1.7.1

These versions now match rules_wasm_component expectations,
resolving "No matching toolchains found for types: @@bazel_tools//tools/cpp:toolchain_type"
error that prevented file_operations_component from building in CI.

Root cause identified through sequential thinking analysis:
Major version jumps in these dependencies introduced breaking changes
in C++ toolchain resolution affecting Rust binaries with C++ linking requirements.

Author: avrabe

MODULE.bazel

@@ -13,10 +13,10 @@ module(
     compatibility_level = 1,
 )
 
-# Core Bazel dependencies - updated to resolve warnings
-bazel_dep(name = "platforms", version = "1.0.0")
-bazel_dep(name = "rules_cc", version = "0.2.0") 
-bazel_dep(name = "bazel_skylib", version = "1.8.1")
+# Core Bazel dependencies - reverted to match rules_wasm_component expectations
+bazel_dep(name = "platforms", version = "0.0.11")
+bazel_dep(name = "rules_cc", version = "0.1.1")
+bazel_dep(name = "bazel_skylib", version = "1.7.1")
 
 # WebAssembly and component support
 bazel_dep(name = "rules_rust", version = "0.62.0")