Can I specify amplify/ directory location for Yarn Workspaces compatibility?

I have the following project structure:

```
workspaces
├── amplify/
├── backend/
└── frontend/
```

Where each workspace is its own git submodule. I would like to tell the CLI that it can find the `amplify/` directory not in `./`, but in `./workspaces`, so that I can call the CLI from the root folder.

As a workaround, I can eliminate the `workspaces/` parent dir and move everything to directory root `./`, so that `./amplify/` is the natural location of the submodule, but ideally I could override this.

I have looked at using `amplify.yml` in root dir `./` to specify `artifacts: baseDirectory: ...` but to not much success.

Start by checking how the CLI is invoked from the repository root and how the mentioned amplify.yml is interpreted. Compare the requested workspaces/amplify/ location with the current ./amplify/ assumption. Done means a documented configuration or supported behavior lets the CLI find the nested directory when run from the root.

Written by the indexing model from the issue text.