chore: bump @financial-times/eslint-config-next from 4.0.0 to 7.1.0

[dependabot]

Bumps @financial-times/eslint-config-next from 4.0.0 to 7.1.0.

Release notes

Sourced from @​financial-times/eslint-config-next's releases.

v7.1.0 Add support for Node 18

What's Changed

• Update to Node 18 by @​ivomurrell in Financial-Times/eslint-config-next#33

Full Changelog: Financial-Times/eslint-config-next@v7.0.0...v7.1.0

v7.0.0

This release is part of the Platforms and Reliability set of scheduled breaking change releases in April.

The breaking changes in this package release are:

• Dropping support for Node.js 14

This will not be a breaking change for your application if it:

• Already runs on Node.js 16

If this is a breaking change for your application because it does not yet run on Node 16 you can follow this guide to migrate from Node.js 14 to Node.js 16

v6.0.0: Upgrade ecmaVersion 2018 -> 2020

Includes changes made in this PR:Financial-Times/eslint-config-next#24

This PR upgrades the index.js config.parserOptions.ecmaVersion from 2018 to 2020 so that it does not throw a parsing error for usage of optional chaining.

Example code

const packageLockJsonStringifiedObject =
	systemNameToHeadBranchPackageFilesMap[camelCase(systemName)] &&
	systemNameToHeadBranchPackageFilesMap[camelCase(systemName)].packageLockJson?.text;

Before

/Users/andy.gout/Documents/dotcom-biz-ops-package-updater/src/task.js
  175:81  error  Parsing error: Unexpected token .

After

No error

Breaking Changes

It is possible that ECMA version 2020 throws errors for syntax that was previously acceptable in version 2018 and so this has been released as a major change so that consumers are conscious of why this may occur.

v5.0.0

Breaking Changes

This adds two new rules to the default set:

• no-throw-literal

... (truncated)

Commits

• 3e82557 Merge pull request #33 from Financial-Times/nori/upgrade-node
• 3314b76 chore: update to node 18
• 9082c77 Merge pull request #30 from Financial-Times/drop-node-14
• fd58095 Drop Node.js 14 support
• 9170d0c Merge pull request #24 from Financial-Times/upgrade-ecma-version
• 5e5a52d Upgrade ecmaVersion 2018 -> 2020
• 7e712a1 Merge pull request #23 from Financial-Times/throw-errors-pls
• 0b80d88 Error when non-errors are thrown or rejected
• 5e486aa Merge pull request #22 from Financial-Times/nori/scheduled-pipeline
• b66a11a add npm full version to fix build
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)