Allow to provide a different tsconfig path for generated bundle validation

[HarelM]

In continue to the following discussion:
#291 (comment)

And in continue to some reports from users that used the generated d.ts file that was generated from this tool:
maplibre/maplibre-gl-js#934

It would be great to be able to set strict mode on the generated types - i.e. do the validation of the output with typescript strict:true flag.

Workaround

The current workaround that I use is to create a new tsconfig.json file, just to validate the generated d.ts file.
If my library was adhering to strict: true then the types were also adhering to it, but I can't change my entire library to be strict (I tried and failed...).

This is the relevant file for the workaround:
https://github.com/maplibre/maplibre-gl-js/blob/fa7372f0493579a60bdf6ac8f1547deb3bc1bcee/tsconfig.dist.json

{
  "extends": "./tsconfig.json",
  "compilerOptions": {
    "strict": true,
    "types": [
      "geojson",
      "offscreencanvas"
    ]
  },
  "include": [
    "dist/maplibre-gl.d.ts"
  ],
  "exclude": []
}

And I'm using the following command to validate the d.ts file:
npx tsc --project tsconfig.dist.json