feat(#1271): run Java lints from YAML packs via lint key

[VasilevNStas]

fix #1271

What

Adds support for running Java-implemented lints from the same YAML pack
format that XSL lints use, instead of requiring a bespoke Lt*Test.java
class per lint.

A pack can now reference a lint by name:

lint: ascii-only
asserts:
  - /defects[count(defect[@severity='warning'])=1]
document: |
  <object author="tests">
    <comments>
      <comment line="1">привет</comment>
    </comments>
  </object>

How

• New XtLint (a Xtory): reads the lint: key from the pack YAML,
  resolves the lint via PkMono, runs defects(XML) and serializes the
  result into the <defects> document. It plugs into the existing
  Xsline/XtoryMatcher/DefectsMatcher machinery by returning a
  Shift that produces the defects, so XtDefects (the defects: N
  shorthand) and all existing assertions work unchanged.
• LtByXslTest:
  • new testsAllLintsByLintName parameterized test runs packs with a
    lint: key;
  • testsAllLintsByEo and checksLocationsOfYamlPacks skip such packs
    (they have no sheets/XSL counterpart).

Demo packs

The following Java lints are now covered declaratively:

• ascii-only — catches-cyrillic-comment
• reserved-name — allows-custom-name
• incorrect-unlint — catches-unknown-lint
• syntax-version — catches-newer-syntax, allows-older-syntax

This is the pattern @volodya-lombrozo proposed for LtSyntaxVersion and
friends, so future Java lints (and the existing ones) can drop their
hand-written JUnit boilerplate.

Both mvn test (1011 tests) and mvn clean install -Pqulice pass.

[VasilevNStas]

@yegor256 @volodya-lombrozo plz review