Add documents License, Notice and Contributing

Added LICENSE for EPL-2.0.
Added NOTICE containing project information and listing third party dependencies.
Added CONTRIBUTING describing how to build the project and contribute.

CONTRIBUTING.md

+# Contributing to Eclipse sim@openpass
+
+This guide provides all necessary information to enable [contributors and committers](https://www.eclipse.org/projects/dev_process/#2_3_1_Contributors_and_Committers) to contribute to Eclipse sim@openPASS. 
+
+## Eclipse sim@openPASS  
+Eclipse sim@openPASS provides a software platform that enables the simulation of traffic scenarios to predict the real-world effectiveness of advanced driver assistance systems or automated driving functions.  
+
+## Developer resources
+
+  * [sim@openpass Website](https://openpass.eclipse.org/)
+  * Mailing list: Join our [developer list](https://accounts.eclipse.org/mailing-list/simopenpass-dev)
+  * Bugs? [GitLab](https://gitlab.eclipse.org/eclipse/simopenpass/simopenpass/-/issues)
+
+## Eclipse Contributor Agreement
+
+Before your contribution can be accepted by the project team, contributors must
+electronically sign the Eclipse Contributor Agreement (ECA).
+
+* http://www.eclipse.org/legal/ECA.php
+
+Commits that are provided by non-committers must have a Signed-off-by field in
+the footer indicating that the author is aware of the terms by which the
+contribution has been provided to the project. The non-committer must
+additionally have an Eclipse Foundation account and must have a signed Eclipse
+Contributor Agreement (ECA) on file.
+
+For more information, please see the Eclipse Committer Handbook:
+https://www.eclipse.org/projects/handbook/#resources-commit
+
+## Contact
+
+Contact the project developers via the project's "dev" list.
+
+* simopenpass-dev@eclipse.org
+
+## How to contribute
+
+The sim@openpass source code can be found [here](https://gitlab.eclipse.org/eclipse/simopenpass/simopenpass).
+
+To build the project, follow the guide in "pathToRepo\sim\doc\OSI World Setup Guide.pdf".
+
+The branch 'servant' contains the contributions that will be included in the next release. 
+
+### Committer contribution process
+
+1. (you) If needed, create the Issue on GitLab and assign it to yourself.
+2. (you) In GitLab, create a merge request. The related branch will be created from the branch 'servant'. 
+3. (you) Work on it.
+4. (you) Assign the issue to another committer.
+5. (other committer) Review the code. 
+6. (other committer) To merge new branch into 'servant' you can close the merge request via GitLab.

[Reinhard Biegel]

Incorrect numbering

[Arun Das]

Fixed in ccc90cf7