Prepare transfer of code to official eclipse velocitas org

[cpotter302]

Code reviews?!

• meeting with Ecl. Vel. Dev
• document plan on what to do before transfer of code

See #35

EPIC: #9

[cpotter302]

Velocitas agreed to create a seperate repo for the plugin

Code will go to Leda Incubator project. Repository is requested here
https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3412

[bs-jokri]

Todos prior Open Sourcing:

• - request to create upstream repository (if does not exist yet) -> https://github.com/eclipse-velocitas
• - create public fork from upstream repository in account repository
• - adjust artifact coordinates and naming conventions (e.g. artifact id, package name, etc.) for upstream project
• - add license and copyright headers to all files (check Velocitas repositories for examples)
• - make sure no copyrighted material is in the repository (eg run license scanner or check manually) -> run Eclipse dash tool
• - Add project metadata files (README, contributing, License, security, etc according to Eclipse regulations and Eclipse Velocitas conventions)
• - setup build pipeline for new PRs
• - setup build pipeline for new releases
• - (request update of project landing page to reference repo)
• - Setup code scan Implement Linting #97
• - enhance error handling Develop error handling #91
• - enhance test coverage develope sufficient Tests #92
• - adjust title of CONTRIBUTING.md