v0.50.0

Datadog's Community Open Source team is excited to announce version `0.50.0` 🚀 

### Changelog
[View release notes](https://vector.dev/releases/0.50.0)

### Release highlights
* The `opentelemetry` source can now decode data according to the standard [OpenTelemetry protocol](https://opentelemetry.io/docs/specs/otel/protocol)for all telemetry data types (logs, metrics and traces). This eliminates the need for complex event remapping. It greatly simplifies configuration for OTEL -> Vector -> OTEL use cases or when forwarding data to any system that expects OTLP-formatted telemetry.
* A new `varint_length_delimited` framing option is now available which enables compatibility with standard protobuf streaming implementations and tools like ClickHouse.
* Introduced a new `incremental_to_absolute` transform, useful when metric data might be lost in transit or for creating a historical record of the metric.
* A new `okta` source for consuming [Okta system logs](https://developer.okta.com/docs/api/openapi/okta-management/management/tag/SystemLog/) is now available.
* The exec secrets option now supports protocol version v1.1 which can be used with the [Datadog Secret Backend](https://github.com/DataDog/datadog-secret-backend/blob/v1/README.md).

### Breaking Changes
The `azure_blob` sink now requires a `connection_string`. This is the only supported authentication method for now. For more details, see this [pull request](https://github.com/vectordotdev/vector/pull/23351).