[Translator] Add configuration to filter dumped keys by pattern

[Kocal]

We already have the option to choose the domain from which we retrieve keys, but adding a filter on key names (via pattern) would allow for more refined filtering.
Since #3208, there is no longer any tree shaking. Adding this feature could help reduce the size of the generated .js files.

ux_translator:
   keys_patterns:
      - 'app.**'
      - 'foo.*.bar'
      - 'foo.**.bar' 
      - # ...

[smnandre]

There were some discussions about filters per "domain" or "locale" if I remember correctly. Maybe some good ideas to get from there.

I'm curious here.. how/why would you use the key pattern filtering ?

[Kocal]

Filtering by domains and locales is already possible, but not directly by "keys".

I'm curious here.. how/why would you use the key pattern filtering ?

In my previous job, we had an application with ~1700 keys in a single domain, with 6/7 locales. Moving/duplicating certain translation keys would have been a huge pain, added no value, and could have increased the time spent on translations. I believe many teams and applications suffer from this same problem.

Since #3208, there is no tree-shaking anymore.

Adding a (fully-optional) keys patterns filtering feature is IMHO a good alternative, which has the advantage to be both compatible with WebpackEncore and AssetMapper (before #3208, only WebpackEncore would beneficiate from tree-shaking).