Add LCP support

[vbessonov]

Description

This PR adds support for LCP license files (application/vnd.readium.lcp.license.v1.0+json) returned by Circulation Manager during fulfilment of LCP protected books.

Linked PRs:

• PR # 1194 in core
• PR # 1472 in circulation
• PR # 125 in circulation-docker

[vbessonov]

@hokei, could you review this PR?

[kristojorg]

@vbessonov While this will allow a button labeled "LCP License" to show in the UI, I don't think this is the right approach for LCP content, as it doesn't mean anything to the user. How does LCP content work? Does the user download a license file? What do they do with it from there?

[kristojorg]

I think we need a better understanding of how this should work from a user perspective before we support LCP files in the web client

[vbessonov]

@kristojorg, you can find a detailed description here.

Also, you can download an LCP book from the LCP testbed (you can find its description and credentials in the Lyrasis wiki). Once you download a book, you can notice that it doesn't have an extension and because of that it cannot be opened in Thorium or other LCP-compatible client applications without manually adding an extension. This PR force opds-web-client to add .lcpl extension to the LCP books

[kristojorg]

Approving this because it matches our level of support for ACSM. In the future we should show users how to deal with these files, though

[EdwinGuzman]

@vbessonov I can merge this in but can you update the version in packages/opds-web-client/package.json and also update packages/opds-web-client/changelog?

[vbessonov]

@EdwinGuzman, sure, should I increase the minor version or the patch one?

[EdwinGuzman]

I think a patch one is fine for this.

[vbessonov]

@EdwinGuzman, sure, will do. Could you tell me how I should update version in package-lock.json?
I tried to use npm update and npm install --package-lock-only but none of them worked. Can I update package-lock.json manually?

[EdwinGuzman]

You can update it manually if you update the version in package.json, then delete package-lock.json, and then run npm install again.

[vbessonov]

@EdwinGuzman, I tried to delete package-lock.json and then run npm install but it didn't work, new package-lock.json for some reason wasn't created. So I ended up with manually updating the version in package-lock.json, I hope it won't break anything

[EdwinGuzman]

Great, thanks.

[EdwinGuzman]

Just published 0.5.7 to npm.