Enable no-explicit-wrapper-destroy eslint rule in Gitlab
Description
Once the new rule is added to gitlab eslint package and published, we need to introduce it to gitlab codebase.
After checking with other engineers, it was decided, that the most efficient way would be to enable the rule and fix all violations in spec files. The violations could be fixed with eslint --fix command, for the cases where the tests are failing, the wrapper.destroy() call can be brought back and commented with eslint-ignore comment.
Edited by Andrei Zubov