Fix import docs, add WorkloadRule docs, cover import lifecycle w/ test

[Rupam-It]

Summary

• Fix every resource doc's pulumi import example — all five used the wrong
  token format (devzero:index/x:X) instead of the actual registered token
  (devzero:resources:X, per schema.json/generated SDKs), so every
  documented import command in the repo would have failed.
• Fix cluster.md's stale claim that token auto-rotates on import/update —
  the provider deliberately stopped doing that (see
  TestCluster_Update_DoesNotRotateToken) since it was silently invalidating
  a live in-cluster agent's credential on unrelated updates.
• Add docs/resources/workload_rule.md, which didn't exist — includes an
  import note on how autoGenerate is inferred from current_source on
  every Read, not stored as its own field.
• Add TestImport_* for all six resource types (Cluster, NodePolicy,
  NodePolicyTarget, WorkloadPolicy, WorkloadPolicyTarget, WorkloadRule),
  simulating the actual pulumi import code path — Read() called with a
  bare ID and zero-value Inputs/State against a resource seeded directly
  into the backend (as if created outside Pulumi). Each test asserts full
  attribute hydration, a clean/idempotent plan (Diff() for WorkloadRule,
  fixed-point Read() for the rest), and that a post-import Update()
  reaches the backend.
• Add the missing UpdateWorkloadRecommendationPolicy handler to
  fakeBackend — WorkloadPolicy.Update() had no test coverage against it
  until now.

Test plan

• go build ./...
• go vet ./...
• go test ./... (all packages pass, including the new TestImport_*)
• Manual staging smoke test (pulumi import → pulumi preview → edit →
  pulumi up) against a real DevZero environment for at least one
  resource of each type — not run in this PR, follow-up

[gitar-bot]

💡 Quality: Contradictory GPU unit description in workload_rule.md

In docs/resources/workload_rule.md the gpuRule row states units are "GPU millicores" (line 100), while the ResourceRuleConfigArgs.minRequest row says "bytes for memory/GPU" (line 133). These two statements contradict each other for GPU. Pick the correct unit and make both rows agree so users don't misconfigure GPU requests.

_{Was this helpful? React with 👍 / 👎}

[gitar-bot]

Code Review 👍 Approved with suggestions 0 resolved / 1 findings

Fixes broken pulumi import examples across all five resource docs by correcting token format from devzero:index/x:X to the registered devzero:resources:X, removes stale token auto-rotation claim from cluster.md, adds WorkloadRule documentation with import guidance, and introduces comprehensive import lifecycle tests for all six resource types including the previously untested UpdateWorkloadRecommendationPolicy handler. Consider clarifying GPU unit descriptions in workload_rule.md—gpuRule states "GPU millicores" while ResourceRuleConfigArgs.minRequest says "bytes for memory/GPU", which conflict for GPU requests.

💡 Quality: Contradictory GPU unit description in workload_rule.md

📄 docs/resources/workload_rule.md:100 📄 docs/resources/workload_rule.md:133

In docs/resources/workload_rule.md the gpuRule row states units are "GPU millicores" (line 100), while the ResourceRuleConfigArgs.minRequest row says "bytes for memory/GPU" (line 133). These two statements contradict each other for GPU. Pick the correct unit and make both rows agree so users don't misconfigure GPU requests.

🤖 Prompt for agents

Code Review: Fixes broken `pulumi import` examples across all five resource docs by correcting token format from `devzero:index/x:X` to the registered `devzero:resources:X`, removes stale token auto-rotation claim from cluster.md, adds WorkloadRule documentation with import guidance, and introduces comprehensive import lifecycle tests for all six resource types including the previously untested `UpdateWorkloadRecommendationPolicy` handler. Consider clarifying GPU unit descriptions in workload_rule.md—`gpuRule` states "GPU millicores" while `ResourceRuleConfigArgs.minRequest` says "bytes for memory/GPU", which conflict for GPU requests.

1. 💡 Quality: Contradictory GPU unit description in workload_rule.md
   Files: docs/resources/workload_rule.md:100, docs/resources/workload_rule.md:133

   In docs/resources/workload_rule.md the `gpuRule` row states units are "GPU millicores" (line 100), while the `ResourceRuleConfigArgs.minRequest` row says "bytes for memory/GPU" (line 133). These two statements contradict each other for GPU. Pick the correct unit and make both rows agree so users don't misconfigure GPU requests.

_{Was this helpful? React with 👍 / 👎 | Gitar}