oas v2 rules applied to v3 spec

[stevenh]

When running vacuum against an openapi v3 spec it still reports failures for oas2-* rules for example oas2-api-host.

I would expect it to only apply the rules appropriate to the spec version.

Example header which I would expect the rules to consider.

openapi: 3.0.0

[stevenh]

Looks like the issue occurs when --skip-check is requested, which seems to be an unintended side effect

[daveshanley]

Hmmm.. interesting. --skip-check should not lose fidelity on which spec is being looked at, it should just stop erroring out if it's not an openapi spec.