bootstrapProfile property marked as IntelliSense error for Managed Cluster Properties (Visual Studio Bicep Extension)

**Bicep version**
run `bicep --version` via the Bicep CLI, `az bicep version` via the AZ CLI or via VS code by navigating to the extensions tab and searching for Bicep
0.28.1
Visual Studio Bicep version = 0.28.1.47646

**Describe the bug**
A clear and concise description of what the bug is vs what you expected to happen

The extension reports a warning : Severity Code Description Project File Line Suppression State
Warning (active) https://aka.ms/bicep-type-issues The property "**bootstrapProfile**" is not allowed on objects of type "**ManagedClusterProperties**". Permissible properties include "aadProfile", "addonProfiles", "agentPoolProfiles", "apiServerAccessProfile", "autoScalerProfile", "autoUpgradeProfile", "azureMonitorProfile", "disableLocalAccounts", "diskEncryptionSetID", "enablePodSecurityPolicy", "enableRBAC", "fqdnSubdomain", "httpProxyConfig", "identityProfile", "kubernetesVersion", "linuxProfile", "networkProfile", "nodeResourceGroup", "oidcIssuerProfile", "podIdentityProfile", "privateLinkResources", "publicNetworkAccess", "securityProfile", "serviceMeshProfile", "servicePrincipalProfile", "storageProfile", "supportPlan", "upgradeSettings", "windowsProfile", "workloadAutoScalerProfile". If this is an inaccuracy in the documentation, please report it to the Bicep Team. c:\Users\Mark\source\repos\FyberOn\Infrastructure\Infrastructure\Lab\Bicep\ALTP-AKS-10-Cluster.bicep 172

**To Reproduce**
Steps to reproduce the behavior:

Load this stripped down resource into a module and VS reports the issue:

resource aks2 'Microsoft.ContainerService/managedClusters@2023-11-01' = {
name: clusterName
location: location
identity: {
type: 'UserAssigned'
userAssignedIdentities:{
'${principalId}': {}
}
}
properties: {
dnsPrefix: dnsPrefix
bootstrapProfile: { //<<--- marked as warning
artifactSource: 'Direct'
containerRegistryId: acrId
}
}
}

**Additional context**
Add any other context about the problem here.

Start by inspecting the type definition for Microsoft.ContainerService/managedClusters@2023-11-01 and compare ManagedClusterProperties with the stripped-down resource in the issue. Confirm whether bootstrapProfile and its artifactSource and containerRegistryId fields are missing or incorrectly rejected, then validate that IntelliSense accepts the resource without the warning.

Written by the indexing model from the issue text.