refactor: add npm actions to generate the licenses files

[sbruens]

Ideally this is done at build time instead of manually, but I don't have time to look into that right now. Leaving that for a future PR.

[sbruens]

@daniellacosse I couldn't get it to work properly on workspaces without specifying both the root and workspace package.json, since some dependencies are installed at ./node_modules/ and others at ./workspaces/node_modules/. Open to suggestions.

[daniellacosse]

@daniellacosse I couldn't get it to work properly on workspaces without specifying both the root and workspace package.json, since some dependencies are installed at ./node_modules/ and others at ./workspaces/node_modules/. Open to suggestions.

Perhaps you could have a root license file sent to output that gets appended to the result in each workspace?

Do we need to commit these? Can we just generate them at build time? If not, they should probably live in a LICENSE file at the root of each workspace (e.g. client/LICENSE)?

[sbruens]

Do we need to commit these? Can we just generate them at build time?

That's what I suggested in the PR description. Agree it should be at build time but I don't have time for that right now. This at least brings the license files up-to-date.

If not, they should probably live in a LICENSE file at the root of each workspace (e.g. client/LICENSE)?

They shouldn't live in LICENSE, that's the repo's own license. This file is the file we distribute with binaries to list all dependency licenses.

[sbruens]

@daniellacosse I couldn't get it to work properly on workspaces without specifying both the root and workspace package.json, since some dependencies are installed at ./node_modules/ and others at ./workspaces/node_modules/. Open to suggestions.

Perhaps you could have a root license file sent to output that gets appended to the result in each workspace?

That doesn't really solve the problem that there's no way to identify which root dependencies belong to which workspace. It's probably fine like this.