Re-add schema priority levels

[JPinkney]

Signed-off-by: Josh Pinkney [email protected]

What does this PR do?

This PR re-adds in schema priority levels. Apparently, they got lost when I refactored everything

What issues does this PR fix or reference?

Is it tested? How?

[coveralls]

Coverage increased (+1.03%) to 78.467% when pulling 712ec0b on schema-priority-levels into 31dbd3c on master.

[ssbarnea]

I am really interested about this change because I currently have a serious issue caused by overlapping file matching patterns, where vscode does not respect a given order. By being able to set priorities I can help it pick the right schema.

This has the potential to address ansible/vscode-ansible#36 with minor changes on ansible extension. At this moment I cannot do anything to make it pick right schema.

[JPinkney]

This PR won't help with ansible/vscode-ansible#36. This has nothing to do with overlapping file patterns. It's related to: #362

[ssbarnea]

This PR won't help with ansible-community/vscode-ansible#36. This has nothing to do with overlapping file patterns. It's related to: #362

My belief was that this would enable me to mention priority levels on https://github.com/ansible-community/vscode-ansible/blob/master/package.json#L103-L156 -- and as a side effect to be able to control which schema is picked.

[evidolob]

LGTM