Update devDependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@types/aws-lambda (source)	^8.10.102 -> ^8.10.106
@types/express (source)	^4.17.13 -> ^4.17.14
@types/jest (source)	^29.0.0 -> ^29.0.3
@types/lodash (source)	^4.14.184 -> ^4.14.185
@types/yargs (source)	^17.0.12 -> ^17.0.13
@typescript-eslint/eslint-plugin	^5.36.1 -> ^5.38.1
@typescript-eslint/parser	^5.36.1 -> ^5.38.1
eslint (source)	^8.23.0 -> ^8.24.0
eslint-plugin-functional	^4.2.2 -> ^4.4.0
eslint-plugin-jest	^27.0.1 -> ^27.0.4
fast-glob	^3.2.11 -> ^3.2.12
hardhat-deploy	^0.11.13 -> ^0.11.15
hardhat-gas-reporter	^1.0.8 -> ^1.0.9
jest (source)	^29.0.2 -> ^29.0.3
lerna (source)	^5.5.0 -> ^5.5.2
solidity-coverage	^0.7.21 -> ^0.8.2
ts-jest (source)	^29.0.0 -> ^29.0.2
typescript (source)	^4.8.2 -> ^4.8.3

---

Configuration

📅 Schedule: Branch creation - "before 2am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, click this checkbox. ⚠ Warning: custom changes will be lost.

---

This PR has been generated by Mend Renovate. View repository job log here.

[andreogle]

Looks like eslint-plugin-functional is now complaining about mutating arrays. I'm guessing we want to disable this?

[andreogle]

I've tested locally and the following change fixes the build:

// .eslint.fp.js

- 'functional/immutable-data': ['error', { assumeTypes: true }],
+ 'functional/immutable-data': ['error', { assumeTypes: { forArrays: false, forObjects: true } }],

I personally would prefer to rather stick with immutable arrays everywhere but I've got a feeling that not everyone feels the same way

[Siegrift]

I personally would prefer to rather stick with immutable arrays everywhere but I've got a feeling that not everyone feels the same way

Looking at the code violations, fixing them seems like a big effort and the current implementation is convenient. I'd disable the warnings (at least for now).