[JavaScript] Refactor unmatched closing tags

This commit reduces amount of contexts pushed on stack
to handle unmatched tags. As new merged context shares patterns with
`jsx-expect-tag-end` compiled syntax cache doesn't change.

JavaScript/JSX.sublime-syntax

@@ -83,14 +83,19 @@ contexts:
     - match: /
       scope: punctuation.definition.tag.begin.js
       set:
-        - jsx-meta-unmatched-tag
-        - jsx-expect-tag-end
+        - jsx-expect-unmatched-tag-end
         - jsx-tag-name
     - match: (?=\S)
       set:
         - jsx-tag-attributes
         - jsx-tag-name
 
+  jsx-expect-unmatched-tag-end:
+    - meta_include_prototype: false
+    - meta_scope: invalid.illegal.unmatched-tag.js
+    - meta_content_scope: meta.tag.js
+    - include: jsx-expect-tag-end
+
   jsx-child-tag:
     - match: <(?=\s*[/>{{jsx_tag_name_start}}])
       scope: punctuation.definition.tag.begin.js
@@ -118,11 +123,6 @@ contexts:
       pop: 1
     - include: else-pop
 
-  jsx-meta-unmatched-tag:
-    - meta_include_prototype: false
-    - meta_scope: invalid.illegal.unmatched-tag.js
-    - include: immediately-pop
-
   jsx-tag-attributes:
     - meta_content_scope: meta.tag.attributes.js
     - match: '>{2,}' # ignore invalid punctuation

JavaScript/TSX.sublime-syntax

@@ -29,8 +29,7 @@ contexts:
     - match: /
       scope: punctuation.definition.tag.begin.js
       set:
-        - jsx-meta-unmatched-tag
-        - jsx-expect-tag-end
+        - jsx-expect-unmatched-tag-end
         - jsx-tag-name
     - match: (?=\S)
       set: