[Feature Request] PNPM mono repo setup is sub-optimal

Description

The way the repo is configured, which I'm guessing happened over time, has led to odd mechanics when working on the code.

ESLint and Prettier are configured to work within the {root}/packages/graph-explorer folder, but not from the root. This means I need to open VSCode at that folder to have the configuration work properly in the editor.

It's also unclear how to manage dependencies. There are pnpm-lock.yaml files at the root and inside each package folder. Typically, mono repos will have a single lock file at the root and everything is managed from the root, never the package folders.

Developers should be able to open the code base from the root folder and work within both the React app and the server app using the same editor. Further, ESLint and Prettier should be setup to work across the entire code base.

Preferred Solution

[x] Update PNPM
[x] Move ESLint configuration up to the root
[x] Move Prettier configuration up to the root
[x] Move VS Code settings up to the root
[x] Remove old lock files in subfolders
[x] Add helper alias for working with packages within workspace
[x] Update documentation

Additional Context

Other potential improvements that will likely be separate pull requests or issues:

[ ] Rename React app package
```
graph-explorer -> ui
```
[ ] Rename server app package
```
graph-explorer-proxy-server -> server
```
[ ] Let Prettier update format of server code and config files
[ ] Fix ESLint errors in server
[ ] Convert server to TypeScript
[ ] Add script to reload server when changes are made in dev

[!TIP] Please use a 👍 reaction to provide a +1/vote.

This helps the community and maintainers prioritize this request.

[!IMPORTANT] If you are interested in working on this issue or have submitted a pull request, please leave a comment.

aws / graph-explorer