Convert them to the matching https equivalent.
probably gitlab specific, but works for now..

Instead of going through the rollup plugin. Turns out the rollup plugin
api shouldn't be used outside of rollup.

Ideally this should give us the same path resolution anyway, even though it's
potentially a different implementation.

It tries to call a resolve method which doesn't exist somehow.
Mock it to get things back to the old behaviour.

Fixes #22

In case we want to get the package path of the current package, but it
isn't in node_modules (as is the case with yarn2) we need to find it
ourselves.

In case the package.json in the current dir has the same name we just use
it as a base. This is after rollup lookup failed, so this is just a fallback.

This was required by an upgrade to OpenSSL 1.1.1j (2021-02-16)

This is used in various packages, so clean it up and add it
to rollup.utils.js.

Takes a package name and a dest path. This way we can more eassily change the
layout and it will error out on package name typos or missing packages.

as is the case with font packages

Instead of hardcoding the paths of the node_modules directory we use the node-resolve
plugin of rollup to find the root of the corresponding JS package and calcucate a path from
there.

Resolving a package requires calling an async function, so we have to use await in the rollup config.
Luckily rollup supports configs wrapped in a promise, so we just have to wrap it in a function which returns
a promise.