[BUG] The SiteAlias parameter is not taken into account by New-PnPSite cmdlet

Reporting an Issue or Missing Feature

The SiteAlias parameter has no effect when running New-PnPSite.

Expected behavior

According to Example 10 in the documentation of this cmdlet:
This will create a new Modern Team Site collection with the title 'Team Contoso' and the url 'https://tenant.sharepoint.com/sites/contoso-site' or 'https://tenant.sharepoint.com/teams/contoso-site' based on the managed path configuration in the SharePoint Online Admin portal. The underlying M365 Group will have 'contoso' as the alias.

Actual behavior

I have run the exact same command as in this example:
New-PnPSite -Type TeamSite -Title 'Team Contoso' -Alias contoso -SiteAlias contoso-site

I could see the output "https://tenant.sharepoint.com/sites/contoso", and corresponding site has been created but with contoso instead of contoso-site.

Steps to reproduce behavior

$rootConnection = Connect-PnPOnline -Url $url -ClientId $clientId -Thumbprint $tumbprint -Tenant $tenant -ReturnConnection -ErrorAction SilentlyContinue
New-PnPSite -Type TeamSite -Title 'Team Contoso' -Alias contoso -SiteAlias contoso-site -Connection $rootConnection -ErrorAction Stop

What is the version of the Cmdlet module you are running?

As the script is running in PS 5:
Import-Module PnP.PowerShell -RequiredVersion 1.12.0 -DisableNameChecking:$true -ErrorAction Stop

Which operating system/environment are you running PnP PowerShell on?

• [X ] Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

Start at the New-PnPSite cmdlet implementation and compare its handling of -Alias and -SiteAlias with the documented Example 10. Reproduce the issue with PnP.PowerShell 1.12.0 using the supplied command; done when the created URL uses contoso-site while the Microsoft 365 Group alias remains contoso.