tf provider api alignment

[ahsan0608]

This MR updates the Terraform provider generation/alignment flow to match recent API changes while keeping the pipeline stable for release.

What changed

• Updated generator path mappings for renamed API path params (vm_id, sg_rule_id, volume_id)
• Added/updated generator schema ignore rules for known codegen collision patterns
• Updated provider compatibility logic for regenerated SG rule and volume models
• Adjusted provider-spec post-processing to keep generation stable in current compatibility mode
• Kept task gen, go test ./..., and task build passing

Validation

task gen ✅
go test ./... ✅
task build ✅

[shuvo072]

Thanks @ahsan0608 for fixing the task gen command — task gen followed by task build works correctly for me now.

Just wanted to clarify the broader scope here: my understanding is that the main goal is to onboard the new Kubernetes APIs (e.g., node groups, nodes CRUD, etc.) into the Terraform provider. I believe this would involve updating build/generator-config.yml to include the new API endpoints, followed by regenerating, building, and testing the provider against those new resources.

Could you confirm if that's aligned with your understanding as well? Happy to discuss further if needed.

cc : @shahedex

[ahsan0608]

Thanks @shuvo072 , yes, fully aligned with your understanding.

This MR’s scope is to stabilize the current generation/build pipeline after API/schema drift (so task gen + task build are reliable again).
The Kubernetes API onboarding (node groups, nodes CRUD, etc.) is the next scope.
I can open a follow-up MR (or Jira set) specifically for Kubernetes onboarding so we can review that separately