improve error messaging when CLI is unable to resolve project path (e.g. after moving the project to a different directory)

### 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/master/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

### How did you install the Amplify CLI?

_No response_

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

_No response_

### Amplify CLI Version

7.6.13

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

No

### Amplify Categories

notifications

### Amplify Commands

add

### Describe the bug

When I tried adding notifications using `amplify add notifications` I started seeing this error below,

I have added a default configuration for **auth** with federal identities.

### Expected behavior

I was expected to enter my FCM cloud messaging credential input.

### Reproduction steps

1. Create an app using amplify init
2. Add auth with the default configuration and federal identities
3. add storage
4. add API
5. Add notification,

Started seeing this error.

### GraphQL schema(s)

```graphql
# Put schemas below this line

```

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

報告されている Mac のセットアップで、`amplify init`、フェデレーション ID を使用するデフォルト認証、storage、API、および `amplify add notifications` を使って問題を再現します。まず、レポートに示されている CLI のパス解決エラーから着手します。完了の条件は、プロジェクトパスを解決できない理由を失敗時のエラーが説明し、現在のエラーの代わりに明確な次のステップを示すことです。

索引モデルが issue の本文から書いたものです。