Make inferred target more customizable with glob pattern

[evanliomain]

Inferred targets are great to not duplicating target configuration in project.json libs. However, it did not tackle a great drawback of using Nx: the duplication of configuration files.

I mean, for a librairie that contain a reusable component, I have eslint, stylelint, jest and storybook plugins on it, and it make me have 6 configuration files.
I have actually 192 of this kind of librairies, so 6*192 = 1152 files that are similar and do not provide usefull content.

Moreover, it pollute merge request review.

Actually, inferred targets watch if this configuration files are present in the librairie to be defined. But I think it's a mistake to stick with this files. It could be more flexible to watch if some kind of files exists, base on customizable glob pattern.
For example:

• If I have a file ending with stories.ts, so targets storybook, build-storybook and test-storybook should be on
• If I have a file ending with spec.ts, so target test should be on
• If I have a file ending with .css or .scss, so target stylelint should be on
• and so on.

To base on a glob pattern could be the first step to remove a lot of configuration files.