Add support for extendedPublishConfig, apply to workspace resolver

[sgb-io]

Thanks @steveukx for providing prior art in git-js! My implementation is very similar, but I've come up with some alternative naming, let me know what you think.

• Adds a script to the root which enables a extendedPublishConfig block in the package.json of any packages in the project. The idea is that we can make changes to the project before publishing, very similar to the native publishConfig option, however, is not restricted to what fields we can change.
• All items in extendedPublishConfig will override fields of the same name at publish time
• We also remove scripts, since they are useless in published packages. This isn't required to achieve the desired result here, but could help avoid confusion should a user attempt to use scripts in the wrong way
• Applied extendedPublishConfig to the workspace resolver package. In this case, we have made the main and types fields change to the built versions at publish time.

The end result is that developers no longer need to build the workspace resolver package in local dev - the dependency can be imported right away, and the types just work.

[changeset-bot]

🦋 Changeset detected

Latest commit: 11b3d0c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@modular-scripts/workspace-resolver	Patch
modular-scripts	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[sgb-io]

Technically this is directory names. I figured that having a hardcoded static list of packages to apply this to, is fine for the scope of this project.

[coveralls]

Coverage increased (+0.1%) to 33.724% when pulling 11b3d0c on sgb-io:feat/use-workspace-resolver-without-build into 1287b1b on jpmorganchase:main.