Fix duplicate code snippet label and add connection string example in azure-messaging-eventhubs README

[Copilot]

The label com.azure.messaging.eventhubs.eventhubproducerclient.construct appeared twice in the README, causing validation failures. Additionally, the "Create an Event Hub producer using a connection string" section incorrectly showed credential-based authentication instead of a connection string example.

Changes

• Removed duplicate label from line 120 (connection string section)
• Label retained at line 156 (DefaultAzureCredential section) where it references the actual source code snippet
• Added new code sample createProducerWithConnectionString() in EventHubsJavaDocCodeSamples.java with label com.azure.messaging.eventhubs.eventhubproducerclient.connectionstring
• Updated README line 120 to reference the new connection string example, properly demonstrating how to create an EventHubProducerClient using a connection string

The connection string section now correctly shows connection string-based authentication, while the DefaultAzureCredential section shows credential-based authentication, ensuring each section accurately represents its intended authentication method.

• Fixes [Java SDK][azure-messaging-eventhubs] Extra Label #47153

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Java SDK][azure-messaging-eventhubs] Extra Label</issue_title>
<issue_description>1.
ErrorInfo: Extra label found: <xref
ErrorLink: https://learn.microsoft.com/en-us/java/api/com.azure.messaging.eventhubs.eventhubclientbuilder?view=azure-java-stable&branch=main
ErrorLocation:

• Appears 1 times , label : <xref

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Java SDK][azure-messaging-eventhubs] Extra Label #47153

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[samvaity]

@copilot Add one com.azure.messaging.eventhubs.eventhubproducerclient.connectionstring example in EventHubsJavaDocCodeSamples and reference it here instead.

[Copilot]

Added the connection string example in EventHubsJavaDocCodeSamples.java with label com.azure.messaging.eventhubs.eventhubproducerclient.connectionstring and updated the README to reference it. The section now properly demonstrates creating a producer using a connection string as intended. (commit 41b006b)

[Copilot]

Pull Request Overview

This PR updates the Event Hubs authentication documentation in the README to prioritize connection string-based authentication over token credential-based authentication. The main example under "Authenticate the client" is changed from using DefaultAzureCredential to using a connection string, and a new code sample method is added to support this documentation change.

• Changed the primary authentication example in README from DefaultAzureCredential to connection string
• Added createProducerWithConnectionString() method to EventHubsJavaDocCodeSamples.java
• Updated README code snippet reference from eventhubproducerclient.construct to eventhubproducerclient.connectionstring

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
EventHubsJavaDocCodeSamples.java	Added new method demonstrating Event Hub producer creation using connection string
README.md	Changed the primary authentication example from DefaultAzureCredential to connection string

[github-actions]

Hi @copilot. We've noticed that new changes have been pushed to this pull request. Because it is set to automatically merge, we've reset the approvals to allow the opportunity to review the updates.

Hi @samvaity. We've noticed that new changes have been pushed to this pull request. Because it is set to automatically merge, we've reset the approvals to allow the opportunity to review the updates.

[github-actions]

Hi @copilot. We've noticed that new changes have been pushed to this pull request. Because it is set to automatically merge, we've reset the approvals to allow the opportunity to review the updates.