Network Observability Operator Seamless Upgrades

Goal:  To improve the UX for Network Observability Operator upgrades, so they don't have to, for example, manually delete objects for a successful upgrade. 

Why is This Important:

Reach next OLM operator capacity level, which is "seamless upgrade":

• https://sdk.operatorframework.io/docs/overview/operator-capabilities/#level-2---seamless-upgrades

Note: the upgrade path currently works for the operator itself, but not for the operands: when upgrading, the users may first have to delete FlowCollector.

Some use cases and links possible implementations: https://docs.google.com/document/d/1LaPNubkZt4q8w7gDA1TT-KRVy5mKFxkGYo_aLph4qOI/edit?usp=sharing

This Epic cover the following items:

• update to v1beta1 version.
• created conversion webhook using v1beta1 as the HUB and v1alpha1 as the spoke, till we have a new release with v1beta1 then we can make v1beta1 as the storage version.
• rearrange configs to allow KinD and OpenShift installs since different deployment needs different certifications, to deploy on kind there is new make file option make deploy-kind/undeploy-kind
• add Makefile new target for conversion auto-gen tool

Any new CRD field in netobserv-1.3 will be added to v1beta1 only.

The documentation / release note will need to be updated accordingly.