fix: use new routeOptions object. No more deprecation warnings

[MattJustMatt]

This fixes deprecation warnings because Fastify moved these into their own object, routeOptions.

[serdnam]

Hello! Thank you for making a PR!

I haven't had the time to look at this closely, but if I understand correctly, this routeOptions object was added in a recent minor version wasn't it? I would rather keep compatibility with the entire v4 line until v5 releases by either adding a fallback or just waiting it out.

[MattJustMatt]

Thanks for taking a look! The routeOptions were added in v4.10 which was released in November 2022. I've tested this change back to then.

It's worth noting that this plugin already requires 4.5, so there's a precedent as well.

I'm happy to add backwards compatibility if needed but I'm guessing it should be ok. Anyone using latest fastify with the current version will have two extra log lines for every HTTP request, it's a lot!

Let me know what works best :)

[MattJustMatt]

@serdnam what's the best route forward here?

[serdnam]

Let's go with adding backwards compatibility, add it to this PR and I'll get around to publishing a minor version this weekend.

[MattJustMatt]

@serdnam apologies for the delay on this. I've updated the PR to include back compatibility

[serdnam]

I have published v7.1.0, let me know if you have any issues. https://www.npmjs.com/package/@serdnam/fastify-sentry/v/7.1.0

Sorry for the delay!