Pypi packaging

[ethieblin]

This PR does the following in the purpose of a future publication on pypi.org:

• Update the package metadata
• Update the MANIFEST.in (used for python packaging)
• Change the way the JavaScript files are loaded so that the user can only "pip install" the package and does not have to perform any other node related command before using the package

[ethieblin]

cc @wiresio

[ethieblin]

The metadata contained in the setup.py is what will appear on pypi as author/maintainer name and email. A good practice would be to add an email for author/maintainer, for example, if you have one for the Eclipse Thingweb Project contact list.

What we usually do in my company is that we share a pypi token of the company account and publish python project using this token. But this is in the local .pypirc and does not appear on the repository or package metadata.

Regarding the pypi account publishing to the pypi project (therefore the one creating it): we will have to wait for the eclipse project to have its own account and create its own token ? Or if you have another method to publish it under the Eclipse Thingweb Project name, I trust you.

In any case, I will not publish this package without a pypi token or direct orders from your side. I think it is best if you publish it the way you want on your side.

[egekorkan]

Regarding publishing, thanks for the clarification. We are attempting to get an organization account so that multiple people can publish without sharing any account or token information with each other. It is a bit of a pain though, see https://github.com/pypi/support/issues/3787 where the request is ongoing since December. We have triggered our Eclipse contacts to see if they can get into touch with someone in PyPi. In the worst case, we will create a normal account and share the token/key privately. If we ever get an organization account, the project can be moved there.