exception for rule delete-response-body-empty

below is email thread

> have an issue with this new check: [azure-openapi-validator/delete-response-body-empty.md at develop · Azure/azure-openapi-validator (github.com)](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-openapi-validator%2Fblob%2Fdevelop%2Fdocs%2Fdelete-response-body-empty.md&data=05%7C01%7CJianye.Xi%40microsoft.com%7C6222d64b0bc347a12e8008dac7a9c944%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638041829614445938%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=ZPK2nTs%2FygAHw5fgLx2W9PkPQUiS%2B5ww5vUTt%2B%2BmTBU%3D&reserved=0)
> Fixed our swagger to correctly represent the actual no-content response, but I do not understand the new the .NET SDK that was created (replaced AzureOperationResponse with AzureOperationHeaderResponse. There is no way I can see how to manage/test the long-running-operation from the client side. For instance how do we distinguish between InProgress, Succeeded and Failed (or even Canceled for that matter)?
[RM] Rollback the change and include the 200 response. We do expect the final response schema to be indicated with a 200 response. We will work to fix the linter rule to take care of this scenario for long running operations.