Create ODataError in Non-Success responses

[KenitoInc]

Issues

This pull request fixes issue #2331 .

Description

When we return error messages from the controller e.g

BadRequest("Error Message");
Conflict("Error Message");
Unauthorized("Error Message");
NotFound("Error Message");

The Error Message is serialized as a string and the response is as follows:

{
  "@odata.context":"https://ServiceUri/odata/$metadata#Edm.String",
  "value":"Error Message"
}

In this PR, we add Custom methods in the ODataController that allows us to Create an ODataError from the Error Message hence the response will be Serialized as an Error to achieve the response below:

{
  "error": {
    "code": "400",
    "message": "Error Message"
  }
}

Checklist (Uncheck if it is not completed)

• Test cases added
• Build and test with one-click build and test script passed

Additional work necessary

If documentation update is needed, please add "Docs Needed" label to the issue and provide details about the required document change in the issue.

[xuzhg]

@KenitoInc Thanks for your PR, Yes, it's based on our discussion. However, i'd like to re-think it again.
The question is that: "Do we need to provide these method "NotFound(), BadRequest()" at our side? or Can our customer to implement it at customer side?"
I'd like to involve @mikepizzo to share his thought.

[xuzhg]

🕐

[xuzhg]

need several E2E