Mark Kafka DSM disabled batch consume test flaky for parentId mismatch

[bm1549]

What Does This Do

Updates the @Flaky annotation on test spring kafka template produce and batch consume in KafkaClientTestBase to document the consumer span parentId mismatch failure mode in addition to the previously documented partition ordering issue.

Motivation

The test KafkaClientDataStreamsDisabledForkedTest → test spring kafka template produce and batch consume was observed failing in CI with:

assert span.parentId == parent.spanId

This failure occurs because the else branch of the assertTraces block (used when hasQueueSpan() is false) assumes a deterministic mapping between consumer trace ordering and producer span indices within trace(0). Since SORT_TRACES_BY_ID uses random trace IDs, the consumer-to-producer linkage is non-deterministic.

The test was already annotated @Flaky for a related partition-ordering issue (#3864). This PR updates the annotation message to accurately describe all known failure modes from this same root cause.

Additional Notes

• Failure rate: 1x in 30 days
• The root cause (non-deterministic batch consumer trace ordering) is the same as the existing @Flaky issue
• No functional code changes; this is a test annotation update only

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors

Jira ticket: N/A

[bm1549]

Closing — need to fix the non-deterministic consumer→producer trace mapping rather than update @flaky message

[ygree]

Addressed in #11168