Type definitions that are necessary to not produce type errors should be marked

[JumpLink]

The Idea is use ESLint's no-restricted-syntax for that.

See also #87

[HeavenVolkoff]

Here is an implementation for the rule targetting Gio.Cancellable.connect:

{
  "eslintConfig": {
    "env": {
      "node": false,
      "es2021": true,
      "browser": false,
      "commonjs": false,
      "shared-node-browser": false
    },
    "rules": {
      "no-restricted-syntax": [
        "warn",
        {
          "selector": "CallExpression[callee.property.name='connect'][arguments.length=2][arguments.0.value='cancelled'][arguments.1.type='FunctionExpression']",
          "message": "Calling .connect('cancelled', () => {}) on Gio.Cancellable instances is wrong, see https://gjs-docs.gnome.org/gio20~2.66p/gio.cancellable#method-connect"
        },
        {
          "selector": "CallExpression[callee.property.name='connect'][arguments.length=2][arguments.0.value='cancelled'][arguments.1.type='ArrowFunctionExpression']",
          "message": "Calling .connect('cancelled', () => {}) on Gio.Cancellable instances is wrong, see https://gjs-docs.gnome.org/gio20~2.66p/gio.cancellable#method-connect"
        }
      ]
   }
}

This issue should depend on #94, right?

[JumpLink]

@HeavenVolkoff We do not need to depend this on #94, I think we can just add the option to generate a eslint config. Or what do you think?