feat: AZAPI Provider Migration with Version Management

Major architectural shift from AzureRM provider to AZAPI provider with comprehensive version management.

Architecture Updates:
- Migrated from AzureRM provider to AZAPI provider for direct Azure REST API access
- Implemented unified version-aware resource framework (AzapiResource)
- Added ApiVersionManager for centralized version registry and resolution
- Added SchemaMapper for property validation and transformation

Supported Services:
- Resource Groups: API versions 2024-11-01, 2025-01-01, 2025-03-01
- Storage Accounts: API versions 2023-01-01, 2023-05-01, 2024-01-01

Features:
- Automatic latest version resolution when no version specified
- Explicit version pinning for stability requirements
- Schema-driven validation and transformation
- Migration analysis with breaking change detection
- Version lifecycle management (Active/Deprecated/Sunset)
- Full JSII compliance for multi-language support

Documentation:
- Updated README with both supported services and all API versions
- Added comprehensive code examples for ResourceGroup and StorageAccount
- Fixed broken documentation links to reference existing files
- Added version-specific usage examples

BREAKING CHANGE: Complete migration from AzureRM to AZAPI provider requires updating import statements and resource instantiation patterns.

Author: archit017

.devcontainer/devcontainer.json

@@ -10,15 +10,15 @@
 			"version": "latest"
 		},
 		"ghcr.io/devcontainers/features/go:1": {
-			"version": "1.19"
+			"version": "1.23"
 		},
 		"ghcr.io/devcontainers/features/terraform:1": {
 			"version": "1.5.4",
 			"tflint": "latest",
 			"terragrunt": "latest"
 		},
 		"ghcr.io/devcontainers-contrib/features/tfcdk-cli:1": {
-			"version": "0.17.3"
+			"version": "0.20.8"
 		},
 		"ghcr.io/devcontainers-contrib/features/jest:2": {
 			"version": "latest"