Remove nondeterministic warning for Automation Job Schedule names

**Bicep version**
Bicep CLI version 0.16.1 (d77dcc750a)
VSCode Extension v0.16.1

**Describe the bug**
Receive a warning that an Automation Job Schedule name is nondeterministic.

**To Reproduce**
Per [MSFT documentation](https://learn.microsoft.com/en-us/azure/automation/shared-resources/schedules#create-a-schedule-with-a-resource-manager-template), the newGuid function must be used so Job Schedules can be idempotent.

```
param JobScheduleName string = newGuid()

resource jobSchedule 'Microsoft.Automation/automationAccounts/jobSchedules@2022-08-08' = {
parent: automationAccount
name: JobScheduleName
properties: {
parameters: {
}
runbook: {
name: runbook.name
}
schedule: {
name: schedule.name
}
}
}
```

**Additional context**
This creates confusion during customer deliveries and causes unnecessary churn.

Start by reproducing the warning with the documented Automation job schedule template and the Bicep 0.16.1 behavior described in the issue. Trace the nondeterministic-name diagnostic for the jobSchedules resource type and compare it with the Azure documentation's newGuid pattern. Done means this valid pattern no longer produces the warning without removing appropriate diagnostics elsewhere.

Written by the indexing model from the issue text.