linter: add deprecation code check, linter declarations

[flakey5]

Adds a check to the linter that ensures all of the deprecation codes in doc/api/deprecations.md are in numerical order.

This also required adding linting declarations to the linter (i.e. <!-- md-lint ... -->), since some of the missing deprecations are ignored for whatever reason.

TODO:

• write tests for the check & declarations
• deprecation type check
• cleanup

[flakey5]

cc @ovflowd @araujogui

[flakey5]

The declarations kinda feel retrofitted in but not sure if there's a better way to pass them

[flakey5]

Wdyt of defining these definitions similarly to the rules & reporters? (i.e. have them defined in a declarations/skip-deprecation.mjs, then here we look them up & call them if they exist)

[flakey5]

probably a nicer way to do this loop

[AugustinMauroy]

This test fail because it's use this fixture

Maybe use snapshot instead of fixture

if you use snapshot you ill need:

    "test": "node --test --experimental-test-snapshots",
    "test:coverage": "node --experimental-test-coverage --test",
    "test:update-snapshots": "node --test --experimental-test-snapshots --test-update-snapshots",
    "test:watch": "node --test --experimental-test-snapshots --watch",

and test will look like:

it('should call each rule with the provided entry', (t) => {
    const rule1 = mock.fn(() => []);
    const rule2 = mock.fn(() => []);

    const engine = createLinterEngine([rule1, rule2]);

    engine.lint(assertEntry);

    assert.strictEqual(rule1.mock.callCount(), 1);
    assert.strictEqual(rule2.mock.callCount(), 1);

    t.assert.snapshot(rule1.mock.calls[0].arguments);
    t.assert.snapshot(rule2.mock.calls[0].arguments);
  });