minikube docker-env incorrectly recognizes shell type in PowerShell 7.1.5

[WojciechThomas]

Steps to reproduce the issue:

1. Open PowerShell 7.1.5

2. Run minikube docker-env

3. Minikube displays:

   SET DOCKER_TLS_VERIFY=1
   SET DOCKER_HOST=tcp://192.168.98.100:2376
   SET DOCKER_CERT_PATH=C:\Users\Wojtek\.minikube\certs
   SET MINIKUBE_ACTIVE_DOCKERD=minikube
   REM To point your shell to minikube's docker-daemon, run:
   REM @FOR /f "tokens=*" %i IN ('minikube -p minikube docker-env') DO @%i
   

   as if it was run in CMD instead of Powershell.

If the minikube docker-env is started in Windows 10 built-in PowerShell it works correctly.

If I execute & minikube -p minikube docker-env | Invoke-Expression command in PowerShell 7.1.5 it returns error:

You: The term 'You' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Invoke-Expression: Cannot bind argument to parameter 'Command' because it is an empty string.
Invoke-Expression:
Line |
   1 |  & minikube -p minikube docker-env | Invoke-Expression
     |                                      ~~~~~~~~~~~~~~~~~
     | The string is missing the terminator: '.

The same command in built-in Powershell works without flaws.

Temporary workaround is pointing to the correct version of shell: & minikube -p minikube docker-env --shell powershell | Invoke-Expression