Properly Handle Invalid Type Conversion Errors in Delete REST Requests

[seantleonard]

Why make this change?

Closes #835

• When submitting a REST request on the DELETE endpoint, improper handling of the raised exception when a type fails to be parsed to the expected type results in an HTTP 500 error.
  • e.g. when a primary key value's type in a REST request does not match AND cannot cast to the type in the underlying database column.

What is this change?

• Adds a Try/Catch block in the DeleteSqlQueryStructure code path to match the other 5 references of the parsing method at fault. The Catch block now properly catches the ArgumentException raised and raises a new DataApiBuilderException which signals the runtime to return an HTTP 400 Bad Request error.

How was this tested?

• Integration Test coverage added for Delete REST path AND Insert/Put/Patch/Find paths for full coverage to prevent regressions. Each operation has a different code path which should properly handle cast conversion of the PK.

Sample Request(s)

• REST Request
  URL: DELETE /api/Book/id/{}
  Expected to fail with HTTP 400 Bad Request and NOT HTTP 5XX.

[Aniruddh25]

Waiting for checking GraphQL scenario.

[Aniruddh25]

LGTM, after double checking 1 more question.