[BUG] Interface JitNetworkAccessPolicyInitiatePort is missing the property allowedSourceAddressPrefixes

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/security/resource-manager/Microsoft.Security/stable/2020-01-01/jitNetworkAccessPolicies.json#L704-L724

### API Spec version

2020-01-01

### Describe the bug

The interface `JitNetworkAccessPolicyInitiatePort` is missing the property `allowedSourceAddressPrefixes`.
Currently, it only includes [property `allowedSourceAddressPrefix`](https://learn.microsoft.com/en-us/javascript/api/%40azure/arm-security/jitnetworkaccesspolicyinitiateport?view=azure-node-latest).

Property `allowedSourceAddressPrefixes` definitely exists: Below is the payload when I initiate the JIT policy request from the portal:

```json
{
"requests": [
{
"content": {
"virtualMachines": [
{
"id": "/subscriptions/SUBID/resourceGroups/RGNAME/providers/Microsoft.Compute/virtualMachines/VMNAME",
"ports": [
{
"number": 3389,
"duration": "PT10H",
"allowedSourceAddressPrefixes": [
"IP1",
"IP2",
"IP3"
]
}
]
}
]
},
"httpMethod": "POST",
"name": "a0bd94fd-7b7c-498d-8f0f-5f474b55b018",
"requestHeaderDetails": {
"commandName": "Microsoft_Azure_Compute.ASCArmClient.postInitiateJitRequest"
},
"url": "https://management.azure.com/subscriptions/SUBID/resourceGroups/RGNAME/providers/Microsoft.Security/locations/francecentral/jitNetworkAccessPolicies/default/initiate?api-version=2015-06-01-preview"
}
]
}
```

### Expected behavior

property allowedSourceAddressPrefixes is available in interface JitNetworkAccessPolicyInitiatePort

### Actual behavior

property allowedSourceAddressPrefixes does not exist in interface JitNetworkAccessPolicyInitiatePort

### Reproduction Steps

Go to the Azure portal
open a VM with a JIT policy already configured for multiple IPs
Go to tab Connect
click "Request Access"

In the network tab of the browser, you will see a batch request with the property allowedSourceAddressPrefixes set

### Environment

_No response_