Updates for Fastify v5

[mcollina]

I had to add a bunch of @ts-expect-error to make things pass, as I have no time to understand why the types here are not behaving.

Checklist

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

[bencoder]

Typing issues are due to conflicting differences between @fastify/session and @fastify/secure-session (which does not have regenerate method).

There is a TODO in the code here that would go some way to fixing it:

fastify-passport/src/session-managers/SecureSessionManager.ts

Lines 57 to 58 in 3a05ee0

	// TODO: This is quite hacky. The best option would be having a regenerate method
	// on secure-session as well

Have raised issue in fastify-secure-session to action this TODO so we can tidy that up.

If there's any urgency to this PR then we could approve it as-is with a follow-up ticket here to clean up once the types are improved on secure-session

[robwalkerco]

I've also had a brief investigation of the types issues, and have created a patch PR that resolves them by more explicitly typing the request data as FastifyRequest & { session: FastifySessionObject | Session<any> }.

I've opened a PR against this PR that resolves the type issues (except the @ts-expect-error comments in the tests).

[mcollina]

@dancastillo @Uzlopak @climba03003 fancy a review?

[dancastillo]

LGTM - just one small comment