Improve config validation

[fe3dback]

• [ ] when "allow.depOnAnyVendor" is "true" - we can check that config not contain vendor, commonVendor, deps.*vendor, deps.canUse fields, because it useless.
• [ ] check that vendor.in match at least one dependency from go.mod (should work with replace directive)

[SealOfTime]

If enabled depOnAnyVendor forces consumers to avoid any specific rules regarding vendors, then it'd be harder to switch from not linting vendoring to linting it.

IMO, best workflow would be achieved by making it so presence of vendor-related parameters in deps overrides depOnAnyVendor, so disabling depOnAnyVendor can be done incrementally in big projects:

1. depOnAnyVendor allows all components to use whatever they want
2. one component gets cleaned up and all its dependencies are evaluated, so it gets a specific rule, which restricts it from getting over-coupled again. Meanwhile, all other components can still depend on whatever vendors, they were depending before
3. then repeat second step until all components get specific rules
4. set depOnAnyVendor to false
5. Voila!

[fe3dback]

Yes, interesting idea, it would be more convenient to add rules gradually than to include them all at once in the whole project.