CI for yarn build

[brossetti1]

thoughts for the future:

we can potentially create a CI process to run:

1. yarn build
2. commit build files to project
3. have manual step for publishing the contracts to npm

locally we could potentially ignore the build files and have our CI action keep the repo up to date.

this would accomplish:

1. prs would not be cluttered but build files and we could see just what is changing in the files that are necessary
2. help with a faster process for syncing the changes contracts with the sdk

similar steps could be taken in the sdk to have CI actions for automation of new versions, etc.

just an idea to think about