Update fastify to v5

[Boka44]

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1213145412557891

[ehtesham1996]

For instance this would be breaking change for dependent repo's. Either they use commit specific latest which is as of now
c2ca996f29504941a3806ddd3d7cb803f8b94de9 or they have to follow the migration guide i.e https://fastify.dev/docs/v5.4.x/Guides/Migration-Guide-V5/

[Boka44]

For instance this would be breaking change for dependent repo's. Either they use commit specific latest which is as of now c2ca996f29504941a3806ddd3d7cb803f8b94de9 or they have to follow the migration guide i.e https://fastify.dev/docs/v5.4.x/Guides/Migration-Guide-V5/

@ehtesham1996 We discussed making a v4 or v5 specific branch if needed.

[francesco-ubq]

Approving as per internal slack conversation / sync

[vigan-abd]

update pkg lock as well

[AlexAtrx]

Running npm update --package-lock-only on this branch should refresh the lockfile cleanly.
I verified locally it adjusts package-lock.json and brings npm audit to 0 vulnerabilities (closes the 7 currently flagged on the branch: 4 high, 3 moderate).

That should cover @vigan-abd 's lockfile request.

@Boka44 could you push the refresh on chore/update-fastify?
This PR should be ready to merge once that lands.

[AlexAtrx]

@Boka44
Audit is clean now, thanks.
One small thing: rerunning npm update --package-lock-only still changes package-lock.json for me. Could you push that remaining lockfile diff too?