Incorrect API version classification on powershell snippets

There are several snippets classified as V1 snippets failing on raptor. They contain commands that are available on Beta but not on V1.
Examples include;
get-me-assignments-powershell-V1-executes
get-user-assignments-powershell-V1-executes
get-user-assignments-expand-submissions-powershell-V1-executes
list-accesspackageassignment-powershell-V1-executes
get-agreements-powershell-V1-executes
get-agreement-powershell-V1-executes
get-accesspackagecatalog-powershell-V1-executes
list-accesspackageassignment-powershell-V1-executes
get-user-assignments-expand-submissions-powershell-V1-executes
get-agreements-powershell-V1-execute
get-me-assignments-powershell-V1-executes
get-user-assignments-powershell-V1-executes
get-group-termstore-powershell-V1-executes
get-set-1-powershell-V1-executes
get-accesspackagecatalog-powershell-V1-executes
get-agreement-powershell-V1-executes
get-user-assignments-expand-submissions-powershell-V1-executes
list-accesspackageassignment-powershell-V1-execute
get-user-assignments-powershell-V1-executes
get-me-assignments-powershell-V1-executes
get-agreements-powershell-V1-executes
get-group-termstore-powershell-V1-executes
get-set-1-powershell-V1-executes
get-group-2-powershell-V1-executes
get-entitlementmanagementsettings-powershell-V1-executes

Start by locating the listed PowerShell snippets, such as get-me-assignments-powershell-V1-executes and get-agreements-powershell-V1-executes, and read how their API versions are classified. Run the relevant raptor checks to confirm the failures. Done means the affected snippets are classified with the API version that supports their commands and the checks pass.