Switching terminal causes errors on analytics

### Before opening, please confirm:

- [X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-cli/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-cli/blob/dev/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### How did you install the Amplify CLI?

_No response_

### If applicable, what version of Node.js are you using?

_No response_

### Amplify CLI Version

10.4.1

### What operating system are you using?

Windows

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No

### Amplify Categories

analytics

### Amplify Commands

add

### Describe the bug

When pulling an Amplify backend using WSL and switching to powershell causes errors when adding analytics.

Powershell version: 7
WSL Version: Ubuntu 20.04

Error:

```
The "path" argument must be of type string. Received undefined
```
Note: When using just WSL works as expected.
Using pure powershell works as expected

### Expected behavior

have consistent behaviour.

### Reproduction steps

1. Pull a Amplify app to new folder using amplify headless pull and WSL
2. open powershell
3. amplify add auth
4. amplify add analytics
Observe error

### GraphQL schema(s)

```graphql
# Put schemas below this line

```

### Project Identifier

b504d5d48b4743c48588029fde7d5fe0

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_