fix(cli): #1576 fix nested greenwood type imports from breaking the build

[thescientist13]

Related Issue

resolves #1576

Documentation

(if we can't figure this out)
ProjectEvergreen/www.greenwoodjs.dev#262

Summary of Changes

1. Have Rollup externalize any Greenwood specific packages

See the patch here - thescientist13/greenwood-loops#2

TODO

1. Will need to refine this to make sure it doesn't catch legitimate use cases that are actually exposed through our exports, like the router or active content client
   

[thescientist13]

This may not be something we can cleanly handle, especially if this invokes running / bundling of Greenwood CLI code - #1576 (comment)

[thescientist13]

I think if did want to try and solve this, I wondering if getting around the usage of URL here would bypass the issue entirely? 🤔 🤞
https://github.com/ProjectEvergreen/greenwood/blob/v0.34.0-alpha.2/packages/cli/src/lifecycles/bundle.js#L362

[thescientist13]

I think this will have to be a "documentation" fix, as even if we make this work, this is effectively enabling the bundling of Greenwood into userland code, which we definitely would not want for users.

So instead, let's recommend how to avoid this hazard completely instead - ProjectEvergreen/www.greenwoodjs.dev#262