chore: Support all status codes for delete

[manisha1997]

Fixes

Support 2xx and 3xx for delete status codes

Checklist

• I acknowledge that all my contributions will be made under the project's license
• I have made a material change to the repo (functionality, testing, spelling, grammar)
• I have read the Contribution Guidelines and my PR follows them
• I have titled the PR appropriately
• I have updated my branch with the main branch
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation about the functionality in the appropriate .md file
• I have added inline documentation to the code I modified

If you have questions, please file a support ticket, or create a GitHub Issue in this repository.

[Copilot]

Pull request overview

This PR expands the acceptable HTTP status codes for delete operations in the Twilio REST framework to support all 2xx and 3xx status codes, rather than only returning success for 204 No Content responses. This aligns the delete method's behavior with the fetch method, which already accepts redirects (3xx codes).

Key Changes

• Modified error threshold from >= 300 to >= 400 to accept 3xx redirect responses
• Changed return value logic from checking specifically for 204 to accepting any 2xx/3xx status code

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.

[Copilot]

@manisha1997 I've opened a new pull request, #767, to work on those changes. Once the pull request is ready, I'll request review from you.

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud