We use rollup-extensions.mjs to define common settings for packaging

up extensions. This builds upon common settings used for packaging

assets for Review Board, so it does an import to a sibling module for

handling that.
This import, though, was an absolute import. To resolve it, node had to

walk up the tree looking for a node_modules that provided a

@beanbag/reviewboard. This was finding reviewboard/node_modules,

since that's where package.json lived. There were versioned

dependencies that differed from other packages, so npm install placed

them there where it thought most appropriate. That meant that

node_modules there only contained a handful of packages, and none of

them were @beanbag/reviewboard.
Much of this has been cleaned up for the 8.x branch, and is a large

effort of its own. However, for this specific situation, fixing the

import to be relative instead of absolute ensures that the right module

is picked up when setting up rollup.js.

Successfully built rbintegrations and Power Pack packages.