build follow ups

[holic]

We've done a lot of work with our build setup, but there's a handful of lingering things I came across and left undone:

• should build:protobuf in services package run make protoc-go or should the protoc-ts step have a dependency on protoc-go step?
• are there other outputs to define for services? currently have bin, proto and protobuf
• services package needs clean scripts
• should tsup command or tsup.config.ts explicitly define the output dir? (implicitly uses the tsup default of dist)
• move typechain outputs from default of types/ethers-contracts to typechain
• rethink prepack/postpack so that pack failures don't leave bad files around, or remove the need for it entirely
• consider foundry profiles for abi output vs regular out
  • these are separated because tests/scripts need the full compiled output and abi output only builds what is needed to export abis for downstream use
• move gas report out of cli? #667
• Standardize our approach for .sol and .ts/.js exports living in the same package #652
• refactor(create-mud): templates disable cache in dev #642
• consistent test/lint steps #637
• remove workarounds for .mts, .cjs, etc. files #636
• Consolidate JS build tooling #612
• setup-protoc seems flaky, we should configure it to only run when there's changes to the services package
• noise probably needs a forge build step (and corresponding clean action) for Noise.sol
• should we remove cache (forge cache) as part of clean step?
• figure out how to get docs back into root workspace, make sure it doesn't collide with other things
• move other packages to tsup (std-client, etc)

[alvrs]

rethink prepack/postpack so that pack failures don't leave bad files around, or remove the need for it entirely

this shouldn't be necessary anymore for the packages that use the new "exports" setup in package.json (see #640 (comment)), but we need to update/deprecate the remaining packages