feat(v3-sdk): separate esm / cjs builds

[just-toby]

PR Scope

breaking change to build structure for v3-sdk

Description

updates the build setup for v3-sdk to manually and explicitly create separate cjs and esm builds (plus a types-only version)

How Has This Been Tested?

built the sdk locally, then installed the local build result in another project (universe/apps/web) and verified that it properly resolved the esm version instead of the cjs version

Are there any breaking changes?

there shouldn't be, but technically if an end user is importing incorrectly (by directly referencing any build artifact files) then they'll need to update

(Optional) Follow Ups

PRs to follow will do this for many other SDKs

[just-toby]

• feat(v3-sdk): separate esm / cjs builds #225 👈 (View in Graphite)
• feat(v2-sdk): separate esm/cjs builds #224
• feat(v4-sdk, v3-sdk, v2-sdk): separate esm / cjs builds #226
• feat(router-sdk): separate esm/cjs builds #223 : 1 other dependent PR (#222 )
• feat(universal-router-sdk): separate esm / cjs builds #221
• feat(permit2-sdk): separate cjs and esm builds, remove tsdx #220
• feat(breaking): esm/cjs builds for uniswapx-sdk #218
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.