unexpected migration prompt on `amplify override storage` after `amplify import storage`

### How did you install the Amplify CLI?

pnpm

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

18

### Amplify CLI Version

10.5.1

### What operating system are you using?

mac

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

n/a

### Describe the bug

When running `amplify override storage` when an imported storage resource is present (from `amplify import storage`) we are prompted to migrate the resource to support overrides and subsequently fail on a missing `cli-inputs.json` file.

Note: after importing storage we see a `parameters.json` file available in the resource's directory, where storage resources created with `amplify add storage` produce a `cli-inputs.json` file. This would explain why the CLI thinks it needs to migrate the resource.

### Expected behavior

Fail fast and print a helpful message

```
Overrides are not supported for imported resources
```

### Reproduction steps

1. `amplify init -y`
2. `amplify import storage`
3. `amplify override storage`
4. observe migration prompt

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

### Before submitting, please confirm:

- [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.

Reproduce the behavior with `amplify init -y`, `amplify import storage`, and `amplify override storage`, then trace the storage import and override command entry points. The issue names no source file or test; done means imported resources fail fast with `Overrides are not supported for imported resources` instead of prompting for migration or requiring `cli-inputs.json`.

Written by the indexing model from the issue text.