Update packages

[whilefoo]

Some packages were outdated and by upgrading the packages the types have changed so I had to fix that

Just realized types are broken in CI. So this pull isn't ready.

[gentlementlegen]

I am fine with the update. Out of curiosity, why do we never pin packages to a specific version?

[whilefoo]

tests/main.test.ts(139,18): error TS2339: Property 'incentives' does not exist on type '{ plugins: { status: { name?: string | undefined; description?: string | undefined; command?: string | undefined; example?: string | undefined; uses: { id?: string | undefined; type: "github"; plugin: string | GithubPlugin; with: { ...; }; }[]; skipBotEvents: boolean; }[]; ... 301 more ...; "*": { ...; }[]; }; }'.

@gentlementlegen this test doesn't make sense to make because the config is not correct for the kernel, maybe you meant that as plugin config?

Out of curiosity, why do we never pin packages to a specific version?

I'm not sure, but we probably should. What ends up happening is that we have ^12.1.0 in the package.json but yarn install will install 12.6.0 which might break something even though it shouldn't according to the convention.

[gentlementlegen]

@whilefoo I think this test was done before we updated the config, so it was using the old bot config and was valid. I didn't spot it since the test still works due to the mock, I should be changed indeed.

I also agree with that, we should definitely set packages to a specific version moving forward.

[rndquu]

Regarding this CI run

Can we simply:

1. @ts-ignore this line since Expression produces a union type that is too complex to represent. #31 has already taken too much dev effort for a single tsc error
2. Remove this line if incentives is no longer present in the kernel's config