remove local development symlink workaround from rollup.config.js

[thescientist13]

As part of #435 / #618 which added improved support for resolve deeply nested relative paths, a bit of a hack / workaround (the if statement) was added to our rollup.config.js:

/*
  * this is an odd issue related to symlinking in our Greenwood monorepo when building the website
  * and managing packages that we create as "virtaul" modules, like for the mpa router
  *
  * ex. import @greenwood/router/router.js -> /node_modules/@greenwood/cli/src/lib/router.js
  *
  * when running our tests, which better emulates a real user
  * facadeModuleId will be in node_modules, which is like how it would be for a user:
  * /node_modules/@greenwood/cli/src/lib/router.js
  *
  * however, when building our website, where symlinking points back to our packages/ directory
  * facadeModuleId will look like this:
  * /<workspace>/greenwood/packages/cli/src/lib/router.js
  *
  * so we need to massage pathToMatch a bit for Rollup for our internal development
  * pathToMatch (before): /node_modules/@greenwood/cli/src/lib/router.js
  * pathToMatch (after): /cli/src/lib/router.js
  */
if (facadeModuleId && facadeModuleId.indexOf(tokenNodeModules) < 0 && fs.existsSync(path.join(projectDirectory, pathToMatch))) {
  pathToMatch = pathToMatch.replace(/\/node_modules\/@greenwood\//, '/');
}

Ideally, would like to eliminate this somehow to avoid having this necessary conditional to distinguish between a user workspace, and our own local workspace.

[thescientist13]

tracking here too - #550 (comment)

[thescientist13]

Will plan to get this handled as part of #978