Exceptionless: Adds enabling exception less 400 status code

[kirankumarkolli]

UseStatusCodeForBadRequest = true

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).

[xinlian12]

@sdkReviewAgent-2

[kundadebdatta]

Few nit comments, but overall LGTM. Ideal if we could take care of the below:

• nit: Typo in PR title: "Excptionless" → "Exceptionless".
• Unit tests confirming 400 responses are returned as status codes rather than thrown.
• This is also a potential behavior change. Currently, callers relying on catching CosmosException for 400 status codes will silently stop receiving those exceptions. Instead they'll get a ResponseMessage with StatusCode == HttpStatusCode.BadReques. Any consumer code structured like:

try { await container.CreateItemAsync(...); }
catch (CosmosException ex) when (ex.StatusCode == HttpStatusCode.BadRequest) { ... }

would need to change to check ResponseMessage.IsSuccessStatusCode or ResponseMessage.StatusCode May be worth calling this out in the description.

[kirankumarkolli]

Few nit comments, but overall LGTM. Ideal if we could take care of the below:

• nit: Typo in PR title: "Excptionless" → "Exceptionless".
• Unit tests confirming 400 responses are returned as status codes rather than thrown.
• This is also a potential behavior change. Currently, callers relying on catching CosmosException for 400 status codes will silently stop receiving those exceptions. Instead they'll get a ResponseMessage with StatusCode == HttpStatusCode.BadReques. Any consumer code structured like:

try { await container.CreateItemAsync(...); }
catch (CosmosException ex) when (ex.StatusCode == HttpStatusCode.BadRequest) { ... }

would need to change to check ResponseMessage.IsSuccessStatusCode or ResponseMessage.StatusCode May be worth calling this out in the description.

Few nit comments, but overall LGTM. Ideal if we could take care of the below:

• nit: Typo in PR title: "Excptionless" → "Exceptionless".
• Unit tests confirming 400 responses are returned as status codes rather than thrown.
• This is also a potential behavior change. Currently, callers relying on catching CosmosException for 400 status codes will silently stop receiving those exceptions. Instead they'll get a ResponseMessage with StatusCode == HttpStatusCode.BadReques. Any consumer code structured like:

try { await container.CreateItemAsync(...); }
catch (CosmosException ex) when (ex.StatusCode == HttpStatusCode.BadRequest) { ... }

would need to change to check ResponseMessage.IsSuccessStatusCode or ResponseMessage.StatusCode May be worth calling this out in the description.

No Behavior change at-all for the application, its only for the Direct stack on how to handle exceptions

[xinlian12]

✅ Review complete (38:34)

No new comments — existing review coverage is sufficient.

_{Steps: architecture, cross-sdk, history, past-prs, quality, sanity-check, synthesis}