Raise an error when the name in yaml and json files is different for a config

[didiladi]

Is your feature request related to a problem? Please describe.
@JACONDE stumbled upon this issue in #114. When the name in yaml and json files is different for a config, we simply continue, without raising an error.

E.g. here is an example config which runs into this problem:

config:
    - tagging: "tagging.json"
     
tagging:
    - name: "yaml tagging"

{
    "name": "json tagging",
    "rules": [
        ...
    ],
   ...
}

Describe the solution you'd like
We should fail early and raise an error when this happens. The error message should be clear and concise.

Additional context
The implementation of this should wait until #101 is tackled. Special consideration should go to configs, which don't have a name property in its json. E.g. some configs have a display_name property.

[tatomir146]

@didiladi this example is kind of wrong? We have already stated in documentation the name must be a variable. If it's a variable and used in Json then it can be different or am I missing something?

[didiladi]

@tatomir146 Maybe the description above is a bit misleading. Yes, you are right, we stated in the documentation that the name must be a variable. But if a user does not declare a variable for it, monaco simply continues without raising an error. This issue is about checking if the config is "compliant" to our rules, and otherwise rejecting it.

[kbocock-krg]

Would also be great given "less is more" to just do away with the config.yaml and do everything in a clean json way?