feat: remove the need for a storage

[squakez]

While working on #4025 we have introduced the requirement of a storage as a PersistentVolumeClaim. However, I've realized this is actually nothing else than a Maven Proxy [1]. The presence of a storage add some complexity to the management of the operator. We also expect that any enterprise should already have a Maven Proxy, so, it makes sense to use it as a Maven best practice.

We are still able to use a PVC if the user wants to have this further optimization, and I'm adding some documentation to explain how to do that.

[1] https://camel.apache.org/blog/2023/06/camel-k-maven-proxy/

Release Note

feat: remove the need for a storage

[squakez]

@gansheer I had to temporary use root in this PR to be able to build. I'm testing with the RunAsNonRoot solution your proposed in the other PR, however, we still have some problem in the builder pod. The problem is that when we copy contents from Camel K operator into the container image later user by builder pod, the privileges for files are transferred with root. We need to find a way to instruct the builder container image that certain directories have a different set of privileges. This has to be done in Spectrum and S2I, right after we copy those contents.

[squakez]

The fix addressing the concerns in previous comment should be available in container-tools/spectrum#37. Once that got merged and we bump the spectrum dependency we should be able to move back the execution of builder pod with non-root privileges.

[squakez]

Failures are likely due to #4511

[squakez]

The failing check did not fail on previous attempt, merging.

[squakez]

@gansheer FYI, this is merged

[gansheer]

🥳