Fix usage of sublime.score_selector

[BenjaminSchaaf]

ST 4173 tweaks how selector scoring works resulting in LSP no longer functioning.

As per the comment there seems to be a misunderstanding of how sublime.score_selector works. The entire selector must always match for a non-zero score, so if the goal is to check if it's not empty and matches then checking for >= 8 is simply wrong.

[BenjaminSchaaf]

An alternative would be to check sublime.score_selector > 1; although a selector like source would also have a score of 1 and thus not match. It's thus simpler but not as correct.

[jfcherng]

Fwiw

API \ ST version	=4173	<4173
sublime.score_selector("a.b", "b")	0	0
sublime.score_selector("a.b", "")	1	1
sublime.score_selector("a.b", " ")	1	1
sublime.score_selector("a.b", "a")	1	8
sublime.score_selector("a.b", "a.b")	2	16

[rchl]

@jfcherng I think you've mislabeled the columns which confused me on how this could cause things to break. The new build returns 2 for sublime.score_selector("a.b", "a.b"), not the old one.

[jfcherng]

@jfcherng I think you've mislabeled the columns which confused me on how this could cause things to break. The new build returns 2 for sublime.score_selector("a.b", "a.b"), not the old one.

Oh. I use a wrong column title... Fixed.