Removed builders from eventhubs; removed impl Into<String> from eventhubs and AMQP; Fixed time conversion issue with 1-1-0001

[LarryOsterman]

A lot of churn, basically boiling down to 4 changes, related to recent API guideline changes:

1. Removed most builders from Eventhubs API surface (EventData builder is still there because EventData is a fairly complicated structure).
2. Removed most impl Into references from both EventHubs and AMQP.
3. Fixed a time conversion with the 1-1-0001 sentinel value EventHubs uses to represent times that aren't available yet.
4. Added the ability to specify a ServiceBus token to the AMQP layer to allow C++ to continue to use Connection Strings.

CoPilot summary

This pull request includes several changes to the sdk/core/azure_core_amqp module, focusing on improving type consistency and handling optional values. The most important changes involve updating method signatures to use concrete types instead of generics and adding support for an optional token type in authorization methods.

Type Consistency Improvements:

• Updated method signatures in AmqpClaimsBasedSecurityApis, AmqpConnectionApis, AmqpManagementApis, and AmqpSenderApis to use concrete String types instead of generics like impl Into<String>. (sdk/core/azure_core_amqp/src/cbs.rs, sdk/core/azure_core_amqp/src/connection.rs, sdk/core/azure_core_amqp/src/fe2o3/cbs.rs, sdk/core/azure_core_amqp/src/fe2o3/connection.rs, sdk/core/azure_core_amqp/src/fe2o3/management.rs, sdk/core/azure_core_amqp/src/fe2o3/sender.rs, sdk/core/azure_core_amqp/src/management.rs) [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14]

Optional Token Type Support:

• Added an optional token_type parameter to the authorize_path method in AmqpClaimsBasedSecurityApis to allow specifying the type of token used for authorization. If not supplied, "jwt" is assumed. (sdk/core/azure_core_amqp/src/cbs.rs, sdk/core/azure_core_amqp/src/fe2o3/cbs.rs) [1] [2]

Code Simplification:

• Simplified the conversion logic in fe2o3_amqp_types by using direct String values and handling optional values more explicitly. (sdk/core/azure_core_amqp/src/fe2o3/messaging/message_fields.rs, sdk/core/azure_core_amqp/src/fe2o3/messaging/message_source.rs, sdk/core/azure_core_amqp/src/fe2o3/value.rs) [1] [2] [3] [4] [5] [6] [7] [8] [9]

Comment Updates:

• Updated comments to reflect the changes, including the addition of sastoken to the list of spell-checked words. (sdk/core/azure_core_amqp/src/cbs.rs)

These changes collectively enhance the codebase by making it more consistent and easier to understand, while also adding flexibility for handling different token types in authorization scenarios.

[heaths]

Better - almost there - but a couple outstanding questions and requested changes.

[heaths]

LGTM. Just some thoughts about symmetrically implementing PartialEq you could probably avoid.