feat: VMSS - Updated types (#5948)

## Description

### Changes

- Updated tests
- Introduced user-defined type for `extensionCustomScriptConfig`
parameter that is aligned with its [official
documentation](https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/custom-script-windows).
- Added parameters `provisionAfterExtensions` &
`provisionAfterExtensions` to 'extension' child module.
- Added types for parameters `osDisk`, `dataDisks`, `nicConfigurations`,
`extensionHealthConfig`, `winRM` & `publicKeys`
- Fixed incorrect default value of `extensionHealthConfig` parameter
- Added optional `name` property to `nicConfigurations` parameter
- Moved Health-Extension to its own deployment block
- Added `provisionAfterExtensions` property support to all extensions

### Breaking Changes

- Merged `extensionCustomScriptProtectedSetting` parameter into
`extensionCustomScriptConfig`
- Removed support for the CustomScriptExtension extension to
automatically append SAS-Keys to file specified via the
`extensionCustomScriptConfig.fileData` property. Instead, the SAS token
must either be pre-provided with the URL, or either the settings
`extensionCustomScriptConfig.protectedSettings.storageAccountKey` &
`extensionCustomScriptConfig.protectedSettings.storageAccountName` or
(recommended)
`extensionCustomScriptConfig.protectedSettings.managedIdentityResourceId`.
For the latter, you can provide either the full resource ID - or set it
to `''` if you want it to use the VM's system-assigned identity (if
enabled) instead. Note, in either case, the Identity must be granted
access to correct Storage Account scope.
- The updated `osDisk` parameter requires an integer for its
`diskSizeGB` property
- The updated `dataDisks` parameter requires an integer for its
`diskSizeGB` property & the `lun` property (which specifies the logical
unit number of the data disk. Can be an incremental number)

## Pipeline Reference

<!-- Insert your Pipeline Status Badge below -->

| Pipeline |
| -------- |

[![avm.res.compute.virtual-machine-scale-set](https://github.com/Azure/bicep-registry-modules/actions/workflows/avm.res.compute.virtual-machine-scale-set.yml/badge.svg?branch=users%2Falsehr%2FvmssAlignment202509&event=workflow_dispatch)](https://github.com/Azure/bicep-registry-modules/actions/workflows/avm.res.compute.virtual-machine-scale-set.yml)

## Type of Change

<!-- Use the checkboxes [x] on the options that are relevant. -->

- Azure Verified Module updates:
- [ ] Bugfix containing backwards-compatible bug fixes, and I have NOT
bumped the MAJOR or MINOR version in `version.json`:
- [x] Feature update backwards compatible feature updates, and I have
bumped the MINOR version in `version.json`.
- [x] Breaking changes and I have bumped the MAJOR version in
`version.json`.
  - [x] Update to documentation
- [ ] Update to CI Environment or utilities (Non-module affecting
changes)

Author: AlexanderSehr

avm/res/compute/virtual-machine-scale-set/CHANGELOG.md

@@ -2,6 +2,24 @@
 
 The latest version of the changelog can be found [here](https://github.com/Azure/bicep-registry-modules/blob/main/avm/res/compute/virtual-machine-scale-set/CHANGELOG.md).
 
+## 0.11.0
+
+### Changes
+
+- Introduced user-defined type for `extensionCustomScriptConfig` parameter that is aligned with its [official documentation](https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/custom-script-windows).
+- Added parameters `provisionAfterExtensions` & `provisionAfterExtensions`  to 'extension' child module.
+- Added types for parameters `osDisk`, `dataDisks`, `nicConfigurations`, `extensionHealthConfig`, `winRM` & `publicKeys`
+- Fixed incorrect default value of `extensionHealthConfig` parameter
+- Added optional `name` property to `nicConfigurations` parameter
+- Added `provisionAfterExtensions` property support to all extensions
+
+### Breaking Changes
+
+- Merged `extensionCustomScriptProtectedSetting` parameter into `extensionCustomScriptConfig`
+- Removed support for the CustomScriptExtension extension to automatically append SAS-Keys to file specified via the `extensionCustomScriptConfig.fileData` property. Instead, the SAS token must either be pre-provided with the URL, or either the settings `extensionCustomScriptConfig.protectedSettings.storageAccountKey` & `extensionCustomScriptConfig.protectedSettings.storageAccountName` or (recommended) `extensionCustomScriptConfig.protectedSettings.managedIdentityResourceId`. For the latter, you can provide either the full resource ID - or set it to `''` if you want it to use the VM's system-assigned identity (if enabled) instead. Note, in either case, the Identity must be granted access to correct Storage Account scope.
+- The updated `osDisk` parameter requires an integer for its `diskSizeGB` property
+- The updated `dataDisks` parameter requires an integer for its `diskSizeGB` property & the `lun` property (which specifies the logical unit number of the data disk. Can be an incremental number)
+
 ## 0.10.0
 
 ### Changes