Restructure location of new YAML files

Structure could look like this:

• theodolite-benchmarks/
  • definitions/
    • uc1-kstreams/
      • plain-benchmark.yaml Can easily be converted to a config map.
      • operator-benchmark.yaml
      • app-deployment.yaml Kubernetes resources for deploying the benchmark.
      • app-service.yaml
      • app-service-monitor.yaml
      • load-generator-deployment.yaml
      • load-generator-service.yaml
    • uc1-flink/
    • ...
    • uc2-kstreams/
    • ...
• theodolite-quarkus/
  • examples/
    • plain/ (any idea for a better name?)
      • example-benchmark/ Content similar to theodolite-benchmarks/definitions/uc1-kstreams/, without operator CR.
      • example-execution.yaml
    • operator/
      • example-benchmark/ Content similar to theodolite-benchmarks/definitions/uc1-kstreams/, without plain benchmark.
      • example-execution.yaml
  • crd/ The CRDs for Theodolite benchmarks and executions.

If theodolite-quarkus/examples/plain/example-benchmark/plain-benchmark.yaml is a subset of theodolite-quarkus/examples/operator/example-benchmark/operator-benchmark.yaml (and accordingly the execution.yaml), we could think of provinding only one file, covering both deployments.

Ideas for replacing plain are standalone or session, see #209 (closed).