[Core AMQP] Version 2 and its breaking changes

[HarshaNalluru]

• No need to re-export rhea types MessageHeader and MessageProps(ongoing [Service Bus] [Core AMQP] Merge AmqpMessage{Header|Properties} exported from both the libraries #12091)
• Move AmqpMessageHeader and AmqpMessageProeprties from service-bus (ongoing [Service Bus] [Core AMQP] Merge AmqpMessage{Header|Properties} exported from both the libraries #12091)
• New AmqpAnnotatedMessage (ongoing [Service Bus] [Core AMQP] Merge AmqpMessage{Header|Properties} exported from both the libraries #12091)
• Re-export rhea's message as "RheaMessage" and not "AmqpMessage" (ongoing [Core AMQP] AmqpMessage -> RheaMessage 🔗 #12169)
• Followup on [Service Bus] Cross-check types of props in AMQPAnnotatedMessage #12032 to update the types in AmqpAnnotatedMessage, AmqpMessageHeader and AmqpMessageProperties
• Address - satusDescription typo [core-amqp v2] Address satusDescription #9031
• undefined in the entityPath becomes stringified "undefined" - [core-amqp] validate() will string-ize 'undefined' #8105
• Non-breaking - improve typedoc output [Core AMQP] Revisit the generated typedoc and add @internal @ignore tags #12156
• Stop exporting DefaultDataTransformer
  - [ ] Data transformer improvements
  - [ ] decode should not parse JSON?
  - [ ] Give users a way to opt-out of the default JSON serialization/deserialization?
  - [ ] Allow users to provide their own serializer?

[ramya-rao-a]

Consider removing the below after a review

• IotSharedKeyCredential
• IotHubConnectionConfig
• delay
• Timeout
• executePromisesSequentially
• EventHubConnectionStringModel, IotHubConnectionStringModel, StorageConnectionStringModel, ServiceBusConnectionStringModel
• Func
• isIotHubConnectionString
• randomNumberFromInterval
• isNode

Update: These are addressed in #12210

[richardpark-msft]

I'm all for making the encoding/decoding (by default) more basic (string -> bytes) but perhaps only bytes on return. This would make us a bit more consistent with the other languages since they're not doing any auto-decoding. We can still offer the ability to slot in their own decoder/encoder.

[ramya-rao-a]

Data transformer improvements
decode should not parse JSON?
Give users a way to opt-out of the default JSON serialization/deserialization?
Allow users to provide their own serializer

I wouldnt touch this now. I'd prefer Event Hubs and Service Bus approach the encode/decode in the same way. Changing this, or allowing users to opt out of the default behavior or allowing them to provide their own serializer can be done in the future using the same approach for Event Hubs and Service Bus