Makefile & Feature Installation instructions

[AshtonStephens]

Use the following template to create your pull request

Description

• Changes some package names to be more idomatic. emily-operation-lambda -> emily-lambda, etc.
• Change smithy generated source locations so clean command doesn't wipe build.rs file.
• Updates the local tools required to run the repository in README.md
• Adds a Makefile with some emily related commands and general build command.

Note that the Makefile is not complete with all the tools for all the monorepo packages. We should update the Makefile with the commands necessary to develop for the packages as we go.

[AshtonStephens]

Converted to draft until I fix the CI.

[8marz8]

LGTM. I was able to build it successfully following the readme. Just needed to update my CommandLineTools and Node.js (Got clear errors)

[netrome]

It works on my machine 👍

[netrome]

Though one annoying point: pnpm-lock.yaml seems to change whenever I run either make install or make test.

[hstove]

LGTM! The makefile commands work as expected and are helpful.

One note is that, with pnpm, the package-lock.json files shouldn't be being updated (and should be deleted actually). That could indicate you're using both npm install and pnpm install. The pnpm-lock.yaml file at the root of the workspace acts as the lockfile for all workspace packages.

[hstove]

Should we just update this Github workflow to be something like "Run tests", since this will run both rust and JS tests? I'd be fine with that, and if there are Rust / Contract / etc workflows we want separately we can do that.

[AshtonStephens]

Yeah, I'll change this to just be run tests and keep the contracts one because it looks like it does more than just this does. Ideally these wouldn't need to be separate because GitHub workflowss aren't really for testing, they're for preventing regression, and so long as the workflow is blocked when we mess something and we cursorily know why then we're good.

[AshtonStephens]

Though one annoying point: pnpm-lock.yaml seems to change whenever I run either make install or make test.

If you try committing that change locally and then rerunning make install && make test does it change further?

[hstove]

@netrome if you run pnpm -v what version do you have? If it's not 9.x.x, that could be causing the lockfile to change, but I'm not sure.

[hstove]

Ah, yeah the current pnpm-lock file was generated with pnpm version 6, which is why the lockfile is changing. Happens for me too when I run pnpm install after checking out the repo.

[hstove]

I've opened #135 which should prevent accidental usage of different PNPM versions