feat(admin): Add custom converters for collection types

[benjamingeer]

This PR adds implementations of JsonCustomConvert to handle the collections that are objects of the properties administrativePermissionsPerProject and groupsPerProject in the class PermissionsData.

Resolves #92.
Resolves #97.
Closes #98.
Needs dasch-swiss/dsp-api#1505.

[tobiasschweizer]

@benjamingeer This looks good, thank you! I will check this PR with @kilchenmann today.

[kilchenmann]

I wanted to use the builded package of this branch in the knora-ui or in the knora-api-js-lib-test app, but I got on both branches the following errors:

ERROR in node_modules/@knora/api/src/api/endpoint.d.ts(18,9): error TS1086: An accessor cannot be declared in an ambient context.
node_modules/@knora/api/src/api/endpoint.d.ts(22,9): error TS1086: An accessor cannot be declared in an ambient context.
node_modules/@knora/api/src/knora-api-config.d.ts(18,9): error TS1086: An accessor cannot be declared in an ambient context.

The error says it's because of these lines:

    /**
     * The session token
     */
    get jsonWebToken(): string;
    /**
     * The session token
     */
    set jsonWebToken(value: string);

I cleaned everything and I'm not sure if it's an issue from this branch or from somewhere else.

[tobiasschweizer]

I wanted to use the builded package of this branch in the knora-ui or in the knora-api-js-lib-test app, but I got on both branches the following errors:

I have spotted this behavior as well in dasch-swiss/knora-api-js-lib-test#21 when the e2e test ran on travis.

I could reproduce this locally with yarn when building @knora/api.

Please try the following:

• run npm i in your @knora/api project root
• run yalc remove --all
• run npm run yalc-publish

In @knora/api we use npm and have an package-lock.json, but there is not yarn.lock.

Then install the local package in your app with yarn

[tobiasschweizer]

see https://github.com/dasch-swiss/knora-api-js-lib-test/blob/c3e533ebb91361cf81de1eff01603bac7c8dc750/.travis.yml#L39

[kilchenmann]

I could reproduce this locally with yarn when building @knora/api.

Thanks @tobiasschweizer. It's seems to be an issue with the dependencies. npm install fixed it because of missing PhantomJS and core-js. I thought last time it wasn't a problem with yarn. But you're right, we should use npm in this library. Now I can review it..

[kilchenmann]

Looks great. Thanks

[benjamingeer]

Thanks @tobiasschweizer and @kilchenmann for your help with this!