Followup on https://issues.redhat.com/browse/NETOBSERV-2610 

Our current API implementation is inconsistent in terms of default values and optionnal fields.

This impacts the openAPIV3Schema generated and consumed by the console plugin forms and the operator API documentation.

To bypass that, values are taken from the CSVExample in the console plugin

However, that solution is not covering all the cases, especially when the example is lacking values or when the user creates the CR from CLI. In that case, the defaults are still not set and the form will behave inconsistently.

We should revisit all the defaults and set those especially in case of opt out options (loki enable / prometheus enable etc)

An attempt was done but needs to be tested especially in terms of migrations: https://github.com/netobserv/network-observability-operator/pull/2421