Update all non major NPM dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@tsconfig/node18	^18.2.1 -> ^18.2.2
@types/bunyan (source)	^1.8.8 -> ^1.8.9
@types/bunyan-format (source)	^0.2.5 -> ^0.2.6
@types/jest (source)	^29.5.4 -> ^29.5.5
@types/jquery (source)	^3.5.18 -> ^3.5.19
@types/jsonwebtoken (source)	^9.0.2 -> ^9.0.3
@types/node (source)	^18.17.14 -> ^18.17.16
@types/uuid (source)	^9.0.3 -> ^9.0.4
@typescript-eslint/eslint-plugin	^6.6.0 -> ^6.7.0
@typescript-eslint/parser	^6.6.0 -> ^6.7.0
cypress	^13.1.0 -> ^13.2.0
eslint (source)	^8.48.0 -> ^8.49.0
jest (source)	^29.6.4 -> ^29.7.0
sass	^1.66.1 -> ^1.67.0
typescript (source)	~5.1.6 -> ~5.2.2
uuid	^9.0.0 -> ^9.0.1

---

• If you want to rebase/retry this PR, check this box

[xoen]

(As commented in ministryofjustice/hmpps-incentives-ui#602 (comment))

Looks like tests fail with a bunch of the following error:

error TS5110: Option 'module' must be set to 'Node16' when option 'moduleResolution' is set to 'Node16'. https://github.com/kulshekhar/ts-jest/issues/4198 or to do with the new version of TS.

I played with this locally and it looks explicitly set module/moduleResolution as follow in the tsconfig.json solves the issue:

"module": "CommonJS",
"moduleResolution": "Node",

I don't think this changes anything in practice as at the moment it's a node app using CommonJS modules but do we think there is any drawback of adding these to the tsconfig.json?

[xoen]

@ushkarev with this change tests pass, should we go for it so that renovate is finally happy?

AFAICT this change shouldn't change anything in practice (but there is some bug in jest or ts-jest or typescript which causes these errors)