git-revlist: Fix trailing comments (#11)

Fix hash-commented highlighting

Change JSON delimiters to only highlight if valid (#10)

* Change JSON delimiters to only highlight if valid
  All instances of `:` and `,` were being highlighted; a simple check that it is not behind a closing bracket should be done.
  Trailing commas will now be marked invalid.
* Move whitespace checks into lookaheads
* Ditto

Fix JSON values before `}` being highlighted as invalid (#9)

Polish and rename `.git-blame-ignore-revs` grammar (#8)

* Improve tokenisation accuracy of invalid revisions

1. Embedded whitespace characters are now included as part of an error.
2. Errors are now tokenised only once per offending line.

* Accept whitespace before and after a revision name

* Extend coverage of `.git-blame-ignore-revs` sample

Now it clearly displays each valid and invalid pattern, with and without
surrounding whitespace.

* Rename blame-ignore grammar to "Git Revision List"

Rationale: https://github.com/github/linguist/pull/5903/files#r878683609

* Add `number-sign` to comment scopes

* Delete CSON artefact

* Add `fileTypes` array to grammar

Co-authored-by: Nixinova <nixinova@gmail.com>

Add generic hash-commented

For highlighting text files that include hash comments.

Change Git Blame Ignore scope name and one match

- Use `source` as the top-level scope as this is a parsed language.
- Ignore whitespace when checking for invalid characters.

Add git-blame-ignore-revs grammar

Adapted from the generic hash-commented grammar, with highlighting for invalid lines.

Change Git Blame Ignore scope name and one match

- Use `source` as the top-level scope as this is a parsed language.
- Ignore whitespace when checking for invalid characters.

Add git-blame-ignore-revs grammar

Adapted from the generic hash-commented grammar, with highlighting for invalid lines.