feat(NODE-3274): add type hinting for UpdateFilter

[nbbeeken]

This brings in type checking / hinting for UpdateFilter. The tests in helper_types.test-d.ts and at the top of updateX.test-d.ts should cover all the new subtypes that make up the UpdateFilter type.

Additional changes:

• Updated tsd
  • Had to fix type errors picked up by tsd, writeConcern not defining defaults, deps.ts exports not correctly union-ed and then later narrowed
• Added running tsd to checking that the definitions are valid, since it is part of the linting process

[dariakp]

looks like tsc actually doesn't like the lack of typing on write concern; other things we discussed fixing is making sure the update tests use 2 schemas: one strictly defined and one that has a key with type; we want to make sure we clearly identify what we do and don't expect to be assignable in each case

[nbbeeken]

@dariakp I think I've address all the comments, we discussed having more schema examples that would result in mostly duplicating the test/types/community/collection/updateX.test-d.ts. That isn't here because the result of looking into indexed schemas was that there isn't a way to preserve the key's narrowing. We can talk further offline, but this refers to the last example in test/types/helper_types.test-d.ts

[emadum]

LGTM

[emadum]

What motivated pulling this out vs leaving it as Kerberos.initializeClient?

[nbbeeken]

Cus Typescript! tsd has its own version of TS which was a version newer and these lines were throwing errors. You'll notice the deps.ts file needed changes to make the types more accurate. Pulling out the function here after you've narrowed the type makes it exist properly inside the callback below. Where as Kerberos.initializeClient has the error that the property potentially doesn't exist.

I can move the narrowing down into the callback too or just cast this problem away, open to diff solutions here

[emadum]

I think it's fine - slightly less readable, but not so bad as to necessitate a change.