Adds new package @microsoft/sarif-matcher-utils

[scalvert]

The motivation for this change is precipitated by the emergence of jest API compatible frameworks, like vitest. In order to provide the same style expect extension while not depending on jest, it's necessary to extract the core matcher utility into its own package. This allows consumers to import and extend into any framework they wish (so long as it's jest style compatible).

Example of usage for vitest:

import { describe, it, expect } from 'vitest';
import { buildMatcher } from '@microsoft/sarif-matcher-utils';
import Sarif from 'sarif';
import { buildSarifLog } from './build-sarif-log.js';

type MaybeSarifLog = Sarif.Log | unknown;

interface CustomMatchers<R = unknown> {
  toBeValidSarifLog(): R;
}

declare global {
  namespace Vi {
    interface Assertion extends CustomMatchers {}
    interface AsymmetricMatchersContaining extends CustomMatchers {}
  }
}

const toBeValidSarifLog = buildMatcher<MaybeSarifLog>();

expect.extend({ toBeValidSarifLog });

describe('a suite', () => {
  it('can check for a SARIF log', () => {
    let data = buildSarifLog();

    expect(data).toBeValidSarifLog();
  });
});

[eddynaka]