As discussed in PR#5421, capturing `@error` is inconsistent, requiring
deep nesting (or priority) in order to correctly have red backgrounds to
it.
Some queries has this capture, some don't. For consistency purposes,
removing all of them is more preferable.
For re-enabling error, either add `(ERROR) @error` or `(ERROR _ @error)`
to your custom queries.
* Add a bunch of the OO keywords and some of the more unusual block
delimiter types
* Highlight macromodule like module is.
* Highlight new as seen in constructor declarations like
`class blah; function new(...); ... endfunction endclass`
* Make endfunction a @keyword.function. This matches how lua does it.
* Make tasks @keyword.function: tasks in SystemVerilog are more or less just
impure functions
* Highlight casex/casez like case is currently highlighted (previously
these were not highlighted at all)
* Highlight unique, unique0, priority for constructs like
`unique case (...) ... endcase` and `priority if (...) ...`
