bcrs-shared-components: need license files

This may be a way for this company to drum up business, but the idea is sound -- we need LICENSE files for the shared components (anything published) (and indeed all our repos, but I think they have a license file already).

> From: Sebastian from Sandworm.dev
> Date: Mon, Jun 19, 2023, 3:17 a.m.
> Subject: Your NPM package, @bcrs-shared-components/document-delivery is missing a license declaration
> To:
>
> Hello, severinbeauvais,
>
> We’re a team of engineers working on OSS security tools for JS dependencies. We noticed your NPM package, @bcrs-> shared-components/document-delivery, doesn't have a declared license. A license is vital to protect your work and ensure clarity for users and contributors.
>
> We've created an overview page for your package on our website so you can see all its stats and vulnerabilities at a glance:https://sandworm.dev/npm/package/@bcrs-shared-components/document-delivery
>
> Cheers,
> Sebastian & The Sandworm Team

Inspect the published shared components and compare their package metadata with repositories that already contain license files. Add LICENSE files or declarations for every published component, then verify that each affected package clearly identifies its license before publishing.

Written by the indexing model from the issue text.