[jaeger-operator] Breaking change to Jaeger CR creation in 2.31.0+

[mjnagel]

Describe the bug

#368 moved the CRD out of the special chart/crds helm chart folder and into chart/crd. While this did result in the chart making use of the already existing chart/templates/crd.yaml template to install the CRD, the result is that you must install the helm chart without jaeger.create set to true, then upgrade after the CRD has been installed.

If we make use of the chart/crds folder as recommended by the first method here then the CRDs are installed before Helm applies the other manifests. There are other options as well including a pre-install/upgrade job that would apply the CRDs if we need conditional CRD creation or helm templating inside the CRD.

To Reproduce
Steps to reproduce the behavior:

1. Attempt to install the helm chart with jaeger.create: true.
2. Helm install will fail due to CRD not existing.

Expected behavior

All values provided in the chart, such as the ability to install a Jaeger CR with the operator, should be supported.

Version (please complete the following information):

• OS: [e.g. Linux]: MacOS
• Jaeger version: [e.g. 1.8]: Chart 2.31.0
• Deployment: [e.g. bare metal, Docker, Kubernetes, ...]: k3d