Fix DomCrawler memory leak with filter method 

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #10879
| License       | MIT
| Doc PR        | no

Add a public method `destroy` on Translator to reset properties and free memory
You're right, but `gc_collect_cycles` also solve (partialy) the circular reference memory leak. I don't use it, because I want the test prove that there is a issue when GC is not called,