Making dateReviver opt-in/opt-out

[rzeng1]

If there's a use case where the client side wants to see raw values of a Date object, using the dateReviver in client should be optional

Right now, the only workaround is to apply post-formatting, which requires a pre-determined format to check against an indeterminate input

[fredr]

We only use the dateReviver when you share the types with the backend, since you have defined your types as Date, we need to convert them to such. If you don't share the types (don't specify --ts:shared-types) the generated types in the client will currently have string as their type.

[shimonenator]

It's nice to have an escape hatch, thank you @fredr for pointing out how to do so

[rzeng1]

I raised a PR up here to make it opt out on the route level with ability to pass in your own custom dateRev fn

#2415