Verify datadog_archives sink

[neuronull]

• Verify internal event processing metrics are tested via assert_X_compliance test helpers
• Update component_discarded_events_total to match the new instrumentation spec by adding reason to the emitted logs, and intentional to emitted logs and metrics
• Verify that the component correctly emits the correct error events per the component spec

[neuronull]

This comment suggests that the assertion to compliance may not be a simple task.

vector/src/sinks/datadog_archives.rs

Lines 1 to 4 in db64132

	// NOTE: We intentionally do not assert/verify that `datadog_archives` meets the component specification because it
	// derives all of its capabilities from existing sink implementations which themselves are tested. We probably _should_
	// also verify it here, but for now, this is a punt to avoid having to add a bunch of specific integration tests that
	// exercise all possible configurations of the sink.

@tobz indicates that this sink is currently inert and can be ignored for the moment, so will not attempt to undertake the above.

In terms of the rest of the audit- the AWS S3, Azure Blob, and GCP CS sinks are all independently tracked already.

As such, I will mark this as complete.