Restructure ods-core

Is your feature request related to a problem? Please describe.
Ods-core has grown massively over the last releases - we should strive for a clean Structure so People quickly find their was thru

Describe the solution you'd like
Retructure ods-core into a few functional buckets:

A) Components - nexus/jenkins/sonarqube/ods*services

• https://github.com/opendevstack/ods-core/tree/master/jenkins

• https://github.com/opendevstack/ods-core/tree/master/sonarqube

• https://github.com/opendevstack/ods-core/tree/master/nexus

• https://github.com/opendevstack/ods-core/tree/master/ods-document-generation-svc

• https://github.com/opendevstack/ods-core/tree/master/ods-provisioning-app

B) move jenkins jobs underneath jenkins (https://github.com/opendevstack/ods-core/tree/master/jenkins/jobs)- away from the root

• https://github.com/opendevstack/ods-core/tree/master/create-projects
• https://github.com/opendevstack/ods-core/tree/master/delete-components
• https://github.com/opendevstack/ods-core/tree/master/delete-projects

C) consolidate scripts, and and ods-devenv underneath ods-setup

Start by inventorying the root directories named in the issue: jenkins, sonarqube, nexus, the ods-* services, the three project job directories, scripts, ods-devenv, and ods-setup. Map the proposed functional buckets and identify the references affected by moving each directory. Done means the requested components, Jenkins jobs, and setup-related content are reorganized without breaking their existing paths or relationships.