[BUG] Missing UTC timezone issue in case DateTime.MaxValue

Describe the bug Please provide the description of issue you’re seeing. There is returning inconsistence format regarding the ExpiresAtUtc. We can see this line does not return time in UTC like line 186. https://github.com/Azure/azure-sdk-for-net/blob/f83d1822f337c7eb2d8d4014b4932eb81a9b2979/sdk/servicebus/Microsoft.Azure.ServiceBus/src/Message.cs#L183

Expected behavior What is the expected behavior? DateTime.MaxValue.ToUniversalTime();

Actual behavior (include Exception or Stack Trace) What is the actual behavior? DateTime.MaxValue

To Reproduce Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

1. Create service bus using CLI for premium or standard.
2. Time to live is set to DateTime.MaxValue.

Environment:

• Name and version of the Library package used: [e.g. Azure.Storage.Blobs 12.2.0]
• Hosting platform or OS and .NET runtime version (dotnet --info output for .NET Core projects): [e.g. Azure AppService or Windows 10 .NET Framework 4.8]
• IDE and version : [e.g. Visual Studio 16.3]

[axisc]

@amamounelsayed Thanks for the details. Unfortunately, this may be a breaking change.

We will track this internally and will fix it in the upcoming release with the higher major version.

[jsquire]

The Microsoft.Azure.ServiceBus package has been deprecated and is only receiving critical security and bug fixes. Unfortunately, the fix for this does not meet that bar and is not currently planned. As Josh mentioned, this is not an issue with the current generation package, Azure.Messaging.ServiceBus.

Closing this out.