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
to get an accurate estimation of the memory used, you should call `gc_collect_cycles` before `memory_get_usage`