Potential breaking changes in Graph PowerShell SDK due to change/rename of tags

The following tags are missing from the latest metadata for PowerShell.
users.Actions
users.Functions
deviceManagement.Functions
deviceManagement.Actions.

This means that if you try to slice the metadata using the above tags, the service will respond with a 404. e.g. https://devxapi-func-prod-eastus.azurewebsites.net/$openapi?tags=^users.Functions$&title=Users.Functions&openapiversion=3&style=Powershell&fileName=powershell_v2&graphVersion=v1.0&singularizeOperationIds=true.

Therefore, some paths that were assigned those tags, currently have new tags and this would potentially introduce breaking changes in the SDK.
Below is an example of before and after for one of the paths.
Before

After

The change will occur in terms of grouping of paths. e.g. Paths that used to appear under Users. Actions module are now appearing under Calendar module.

Comienza comparando las etiquetas users y deviceManagement en los metadatos vinculados de powershell_v2.yaml con la solicitud de slicing de $openapi mostrada en el issue y, después, inspecciona las agrupaciones de rutas generadas. Se considera terminado cuando las etiquetas afectadas ya no devuelven 404 y las rutas afectadas conservan una agrupación compatible del SDK de PowerShell; revisa el pull request #642 vinculado para consultar el trabajo existente.