Azure Automation Runbook naming issues

### Description

When using powershell to manage Automation runbooks, we get the following error:
'runbookName' does not match expected pattern '^[a-zA-Z]*-*[a-zA-Z0-9]*$
I am running this on an Azure Devops pipeline using Windows-latest image
The runbooks in question have the format for example:
Invoke-ComplianceCheck-Test
This has been the case for several years and is also in line with the resource naming standard. If the standard has changed, the documentation does not reflect this. If the standard has not changed, is there a bug in the latest module?
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftautomation
Renaming these runbooks means around 200+ changes in our environment.

### Script or Debug output

_No response_

### Environment data

_No response_

### Module versions

_No response_

### Error output

_No response_

Start by reproducing the runbookName validation in the Azure PowerShell module from the Windows-latest Azure DevOps environment, using a name such as Invoke-ComplianceCheck-Test. Compare the reported pattern with the linked Microsoft Automation naming rules and determine whether the module behavior or documentation is inconsistent. Done means the discrepancy and required resolution are clearly confirmed.

Written by the indexing model from the issue text.