Allow to define sub-settings by module

[tzi]

There was a problem on how bemlinter linted multi-settings on single-website project:

• In one side: we need to lint all the website stylesheets together, like a browser will use it
• In the other side: we needed to use several bemlinter settings to assure the prefix presence, for example, in a specific folder/module

So I change the bemlinter behaviour to allow settings override in a specific module.

What changed:

• [options] Creation of the file options, to get the linter options for a specific file path
• [result] Every time we stock a reference of a block name, it's now a couple {moduleName, blockName}
• [lint] Allow only one class prefix by module, to allow the linter to retrieve the module from a class name.
  Usage example: There is a style leak (a block styling another block) and we want to mark the external block as errored
• [format] Group the result by module and display the module name before the block name
• [documentation]
• [test]

Extra:

• A test for an invalid stylesheet

😞 Sorry for the fat PR, it is a big change for the bemlinter. There is certainly some improvment to do on the code readability...

[fdubost]

The code is OK for me. However the concept of "project" sounds strange for me. The project is the place where you want to use bemlinter. We want to apply different configs on project subsections. It's maybe "modules" rather than "projects", WYT ? It's just a naming observation 😺

[fdubost]

Oh it seems there is no .editorconfig file in the project to tell your IDE to auto-add an empty line at the end of each file 😜

[tzi]

✅ Done!

[tzi]

@fdubost 👍 The module name is way better.

[tzi]

✅ Rename option to modules: done!