[ServiceBus] the constraint relationship between absolutely expiry time and time to live property on outgoing message

[yunhaoling]

Problem:

• According to comment in JS's PR: [Service Bus] Filling the gaps for AmqpAnnotatedMessage  azure-sdk-for-js#14786 (comment)
  the absolute_expiry_time on uamqp.message.MessageProperties should be calculated based on time_to_live on uamqp.message.MessageHeader:
  

Reason:

• This is a service bus spec, not an amqp spec
  • Harsha mentioned that "service-bus service has a bug that required us to add this"

Todo:

• check with josh/harsha, cross-language consensus on this custom logic
• discuss and conclude on how to deal with it when we're sending AmqpAnnotatedMessage
  • should be we override the absolute_expiry_time/time_to_live? --> yes, it should be dealt with the same way the ServiceBusMessage deals with them (according to discussion with Josh/Harsha)
• Apply the custom logic to outgoing ServiceBusMessage if needed
• Apply the custom logic to outgoing AMQPAnnotatedMessage if needed
• code impacted:
  https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/servicebus/azure-servicebus/azure/servicebus/_common/message.py#L273-L283

as users set the time_to_live, we need to update the absolute_expiry_time of the MessageProperties of the internal amqp message ServiceBusReceivedMessage.message

[swathipil]

MAX_DURATION_VALUE constant added to servicebus/_common/constants, set from here: https://github.com/Azure/azure-sdk-for-js/blob/887eb013a7c9278b7eedb2c04c5e1bac0b984ebe/sdk/core/core-amqp/src/util/constants.ts

MAX_ABSOLUTE_EXPIRY_TIME here:https://github.com/Azure/azure-sdk-for-js/blob/887eb013a7c9278b7eedb2c04c5e1bac0b984ebe/sdk/core/core-amqp/src/util/constants.ts#L75