[BUG]The Name under alwaysReady property of Azure flex consumption function app is always being lowercased

### API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/web/resource-manager/Microsoft.Web/stable/2023-12-01/CommonDefinitions.json#L3675

### API Spec version

2023-12-01

### Describe the bug

The user's input is always being lowercased

### Expected behavior

the api should respect the user's input, for example, if the user's input is "FunctionName", the value should be staying as what it's being passed, instead of being changed to "functionname".

@nzthiago for awareness

### Actual behavior

The value is being lowercased, despite the camel case that's passed by the user

### Reproduction Steps

simple send the value following the example payload:
```
"functionAppConfig": {
"deployment": {
"storage": {
"type": "blobcontainer",
"value": "https://xiaxintest331.blob.core.windows.net/testtfblob1",
"authentication": {
"type": "storageaccountconnectionstring",
"userAssignedIdentityResourceId": null,
"storageAccountConnectionStringName": "DEPLOYMENT_STORAGE_CONNECTION_STRING"
}
}
},
"runtime": {
"name": "python",
"version": "3.11"
},
"scaleAndConcurrency": {
"alwaysReady": [
{
"name": "blobConfig",
"instanceCount": 80
}
],
"maximumInstanceCount": 100,
"instanceMemoryMB": 2048,
"triggers": null
}
},
```

### Environment

_No response_

Start with the linked CommonDefinitions.json definition around line 3675 and inspect how the alwaysReady name property is specified. Reproduce the payload with a camel-cased name such as "FunctionName", then verify the API specification or related behavior preserves the submitted casing rather than lowercasing it.

Written by the indexing model from the issue text.