Remove 'response.deleted' check

[albarin]

What?

The goal of this change is to prevent the tests using the deteleAllTemplates from failing when the response is undefined or null.

Why?

When a template couldn't be deleted the response variable is null, but the code is trying to access the deleted property on it, and giving this error:

TypeError: Cannot read properties of undefined (reading 'deleted')

How?

Removing the response.deleted check. if deleted is present it will be always true, any other error will make the request fail and it'll go on the catch.

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[github-actions]

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @albarin! In case you missed it, we'd love to have you join us in our Slack community, where we hold regularly weekly meetings open to anyone to coordinate with each other.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

[robinwpdeveloper]

Pretty simple fix and does null check properly.

[Mamaduka]

Thanks, @albarin!

[ntsekouras]

Thank you for your contribution @albarin and congrats on your first commit in Gutenberg 🎉

[github-actions]

Congratulations on your first merged pull request, @albarin! We'd like to credit you for your contribution in the post announcing the next WordPress release, but we can't find a WordPress.org profile associated with your GitHub account. When you have a moment, visit the following URL and click "link your GitHub account" under "GitHub Username" to link your accounts:

https://profiles.wordpress.org/me/profile/edit/

And if you don't have a WordPress.org account, you can create one on this page:

https://login.wordpress.org/register

Kudos!