Fixes #513: Renamed deleter methods to destroy

[Sakshi-75]

Please check if the PR fulfills these requirements

• [x] The commit message follows our guidelines
• [x] Tests for the changes have been added (for bug fixes / features)
• [x] Documentation has been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) This PR renames deleter methods in the interop by replacing delete word with destroy to maintain consistent method naming throughout.

Is there an open issue that this resolves? If so, please link it here. Resolves #513

What is the current behavior? (You can also link to an open issue here)

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) No

Other information:

[CLAassistant]

All committers have signed the CLA.

[Sakshi-75]

Hi @RubyNova , I addressed all the PR comments. Can you check if anything got missed? Thanks!

[RubyNova]

All that's really missing is updating the branch with main since something else got merged since this PR was opened. I've enabled auto merge but it won't merge until:

• CI is fully passing
• this branch is up to date with main

The contents of the PR itself is fine. :)