APP-2072 Move prime to packages/legacy in a pnpm workspace.

[ethanlookpotts]

Overview

This PR restructures PRIME to use pnpm workspaces according to the proposal in this wiki. The @viamrobotics/prime package will remain stable for now during our migration to the new structure. This package will be removed once we've completed the move and applications no longer depend on @viamrobotics/prime.

Test Plan

• Verified existing commands work as expected (playground, storybook, etc)

Changelog

• Added pnpm-workspace.yaml
• Moved package under packages/legacy
  • Fixed all path resolution
• Updated READMEs, added new top-level README
• Updated Github Workflows

Review requests

Please pull down this branch and test your normal workflows with PRIME and make sure they work as expected.

[ethanlookpotts]

Please read this section as "to be added soon" 😄

[mrloureed]

LGTM 👏

[DTCurrie]

I can't run pnpm build in packages/legacy and I am seeing this with pnpm storybook:

[ethanlookpotts]

I can't run pnpm build in packages/legacy and I am seeing this with pnpm storybook:

@DTCurrie Can you try again? Did you pnpm install?

[DTCurrie]

I can't run pnpm build in packages/legacy and I am seeing this with pnpm storybook:

@DTCurrie Can you try again? Did you pnpm install?

I did do a pnpm install. I will try again later today.

[mcous]

Re-org looks great! I think these should be all the changes we need to get publishing working with the new structure.

While testing, you can use the dry-run input on the publish step (along with messing with the if) to verify the correct stuff will get published

[ethanlookpotts]

While testing, you can use the dry-run input on the publish step (along with messing with the if) to verify the correct stuff will get published

I validated with dry-run that the correct files would get published. Thank you for the recommendation!

[mcous]

🎉