Summary

Modify the CLF API and operator logic to use the OTEL data model by default
when forwarding to LokiStack
So we can prepare for the OTEL feature to become GA

Acceptance Criteria

• Verify the OTEL data model is used when forwarding to LokiStack and the data model is not defined
• Verify the OTEL data model is used when forwarding to LokiStack and the data model is set to be OTEL
• Verify the ViaQ data model is used when forwarding to LokiStack and the data model is set to be ViaQ
• Verify the API documentation indicates OTEL is the default used when the data model is not defined
• Verify the API documentation indicates the ViaQ datamodel is deprecated when forwarding to LokiStack and that it will be disregarded in a future release
• Verify the CLO upstream documentation is modified to reflect the changed default data model