🐛 Fix GCP network/subnetwork discovery not working + several crashes

[tas50]

A few different issues here.

• Fix some crashes I experienced trying to list out networks + a few other places where we weren't doing nil checks
• Get discovery of networks/subnetworks working
• Update the deps to the latest
• Don't make the individual resources private since we have asset platforms for these

[github-actions]

Test Results

5 397 tests  ±0   5 393 ✅ ±0   2m 7s ⏱️ -1s
  411 suites ±0       4 💤 ±0 
   31 files   ±0       0 ❌ ±0 

Results for commit 4659a28. ± Comparison against base commit 95f5fbc.

♻️ This comment has been updated with latest results.

[mondoo-code-review]

Well-implemented crash fixes with proper nil checks and improved resource fetching

[mondoo-code-review]

Critical compilation error in subnetwork fallback; missing nil checks in fallback paths

Additional findings (file/line not in diff):

• 🟡 providers/gcp/resources/compute.go:1371 — Missing nil checks before accessing args["name"], args["region"], and args["projectId"]. If these keys are absent, this will panic with nil pointer dereference.

[tas50]

Regarding the bot review (CHANGES_REQUESTED):

• "Undefined variable region" — Not an issue. region is defined at the top of initGcpProjectComputeServiceSubnetwork (line 1453) before both the cache lookup and the fallback path.
• "Missing nil checks on args" (lines 1321, 1371, 1505) — This follows the established pattern across all GCP init functions. When len(args) == 0, the values are populated from getAssetIdentifier (or an error is returned). When len(args) > 0, the MQL framework always provides the args defined in the .lr schema. No existing init function in the GCP provider adds nil guards here.

Superseded by new review

[mondoo-code-review]

GCP network/subnetwork discovery and several nil-pointer crashes are fixed, but a bug check on gvnic config was also corrected.