fix/error message missing

[baywet]

fixes #5311

This a PR is a follow up to #4930.

Rather than removing the conflicting errorMessage property, we should rename it and keep the primary message property. The renamed property should then set as IsPrimaryErrorMessage so that the derialized information may be propagated up to the Exception/error info.

[andrueastman]

@baywet I made a few changes here.

I believe that rather that rather than removing the conflicting errorMessage property as we did in #4930, We should rename it and still keep the primary message property.
The renamed property should then set as IsPrimaryErrorMessage so that the deserialized information may be propagated up to the Exception/error info.

This way we get to

• Resolve conflicts between class/ property names (if collisions exist).
• Deserialize the data to the property that is escaped so we don't lose the information over the wire.
• The exception class still gets the message information in the overridden property with thew two properties as below.

        /// <summary>The primary error message.</summary>
        public override string Message { get => MessageEscaped ?? string.Empty; }
        /// <summary>The Message property</summary>
#if NETSTANDARD2_1_OR_GREATER || NETCOREAPP3_1_OR_GREATER
#nullable enable
        public string? MessageEscaped { get; set; }

[baywet]

@andrueastman thanks for your contribution here. I pushed additional commits for the serialization name and the changelog. Ready for review and merge!

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
85.7% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[andrueastman]

👍🏼