Add first_line_match for REG syntax (#18)

Signed-off-by: Jack Cherng <[email protected]>

Remove EditorConfig syntax

Closes #16

The syntax was moved to the EditorConfig package.
If the EditorConfig package is not installed .editorconfig files will
still be highlighted as regular INI files.

Use detailed scope for boolean value (#17)

Just like https://github.com/sublimehq/Packages/blob/b2d1324bf97452c32c9e0065b05b897e05ed122f/JavaScript/JavaScript.sublime-syntax#L1606-L1607

This allows the user to highlight true/false in different colors.

Signed-off-by: Jun-Fei Cherng <[email protected]>

Add more file extensions

* ffpreset, avpreset - https://ffmpeg.org/ffmpeg.html#Preset-files
* desktop - https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html
* lektorproject - https://www.getlektor.com/docs/project/file/
* pycodestyle, .pycodestyle - https://pycodestyle.pycqa.org/en/latest/intro.html#configuration
* pylintrc, .pylintrc - https://pylint.readthedocs.io/en/latest/user_guide/usage/run.html#command-line-options
* vlcrc - https://wiki.videolan.org/Preferences/
* .coveragerc - https://coverage.readthedocs.io/en/latest/config.html
* .flake8 - https://flake8.pycqa.org/en/latest/user/configuration.html#configuration-locations
* .style.yapf - https://github.com/google/yapf#formatting-style

Also see GitHub Linguist: https://github.com/github-linguist/linguist/blob/8a2415b96ad796af16e853ddb091521af919c486/lib/linguist/languages.yml#L2885-L2904

Also moves application specific and not very common extensions into
hidden_file_extensions, so that they are not shown in the file dialogs.
This implicates that those files won't be opened with INI syntax by
default in Sublime Text 3, but in that case it can still be configured
via "extensions" syntax specific setting.

Add keybinding example for alternative comment toggling to README

Replace reg_completions plugin with completion files (#13)

Advantages:

* no more overhead from EventListener / plugin file which needs to be loaded by ST
* can easily use the rich completion format with "kind" icon while still keeping compatibility with ST3

Disadvantages:

* location where completions are triggered is not as precise anymore (hive names are suggested within the entire registry path instead of only right after the opening bracket)

Merge pull request #9 from jfcherng-sublime/feat/section-new-line-scope

Add scope for newline at section end

Remove number highlighting from filepath globs in EditorConfig

Unlike the punctuation characters, the numbers between braces in
filepath globs are still part of the path/filenames. Therefore it is
probably better to not give them special highlighting colors.

Allow to uncomment #-comments with toggle_comment

Add a TM_COMMENT_START_2 setting for #-comments into the metadata file,
which allows to uncomment those kind of comments with the default
keybinding for the toggle_comment functionality (Ctrl + /). Comments
which are added via this keybinding still use a semicolon (defined by
TM_COMMENT_START setting). Afaik there is no way to allow both ; and #
at the same time for different comment styles via separate keybindings
whithout modifying the builtin toggle_comment functionality.

Update GitHub Action

* use syntax test action v2
* rename tests -> test