fix (coverage): remove statements not needed since fastify@3.22.1

[darkgl0w]

Hello.

This PR aims to :

• remove 2 statements that are not needed since the release of fastify@3.22.1
• unlock the upgrade of fastify dependency by our GitHub action workflow
• upgrade package dependencies (fix Update dependencies #470)

For reference:

• the PR that introduced the behavior: Fix content length fastify#2546
• the PR that fixed the behavior: fix: pipe stream inside error handler fastify#3375

Checklist

• run npm run test and npm run benchmark
• tests and/or benchmarks are included
• documentation is changed or added
• commit message and code follows the Developer's Certification of Origin
  and the Code of conduct

[mcollina]

I would just remove both statements, we only support the latest release of Fastify anyway.

Could you bump the fastify dep on package.json too?

[darkgl0w]

Should I bump the minimum required fastify version to >=3.22.1 too ?

Currently require fastify@1.0.0 or greater:

module.exports = fp(fastifyNext, {
  fastify: '>=1.0.0',
  name: 'fastify-nextjs'
})

[Eomm]

Should I bump the minimum required fastify version to >=3.22.1 too ?

Not sure about it because someone out there could be using Fastify v2 and this plugin (and I know this is not a hypothesis).
If we do it, we should bump a major.

[mcollina]

let's bump the minimum dependency on Fastify (and use the ~ instead of the ^) and bump the major.

[darkgl0w]

@Eomm > yeah this is why at first I just added an istanbul ignore next command without removing the check. Like this it allowed to ensure compatibility with old fastify version.

Anyway with those 2 statements being removed we must land this as a major since this is a breaking change with fastify <= v3.22.0

[darkgl0w]

let's bump the minimum dependency on Fastify (and use the ~ instead of the ^) and bump the major.

@mcollina > I already bumped all dependencies to their latest (both in package.json and package-lock.json) it should be enough and with this last change fastify plugin constraints will do the job if it detects an unsupported version ^^

[Eomm]

(waiting before merge: there are a minor in pipeline to release first)