documentation should contain a page with 3rd party licenses

[ogoffart]

For our binary packages, we use cargo-about to generate a list of all licenses of dependencies.
Our rust user can easily do the same donloat all the licenses of their program.
What we should do anyway is to have this generated list on our documentation so that one can see all the dependencies. And maybe user can take this list for their C++ or Js/python.

Ideally we run cargo-about when generating the docs to generate something that can be shown in a section of the docs.

We can also try to see if we can generate machine readable format that can be consumed by users.

[tronical]

What we should do anyway is to have this generated list on our documentation so that one can see all the dependencies.

Since the list of dependencies depends on the choice of programming language / API, I think we need to invoke cargo-about for the documentation of three distributions:

1. C++
2. Node.js (we distribute binaries)
3. Python

In addition, of course, we should continue to ship the output as part of the compiler/viewer/c++ etc. binary packages we ship. But I understand that this ticket is only about the documentation.

[tronical]

This is done for C++ docs and Node.js docs now (and it was already done for the tool and C++ package binaries we ship). I'll remove this from the 1.9 milestone but keep it tagged for Python, so that we remember to add it to the docs there once we cross that bridge.