We no longer bundle keycloak-js with rollup so we can remove those
special cases.

This makes sure the library version works with the server version.

Ideally we'd also want to check the version so we can error out if a too
old keycloak server is on the other side, but I don't see any public API changes
that would allow us to know if the library is too old.

Fixes #32

See #32

I couldn't find any breaking changes affecting us

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.

Since they are no longer in separate repos we no longer need the
gitlab CI config files.

We couldn't do this until now because we referenced them by a relative path with npm.
But now that we reference them by name and yarn handles the linking we can
specify them as normal dependencies.

They are not published yet

No longer needed

Having two base classes for two small methods is a bit much.

Neuber, Eugen Ramon authored 5 years ago and Reiter, Christoph committed 4 years ago

See issue VPU/Apps/Library#38

Fixed upstream: https://github.com/select2/select2/issues/5682