fix: correctly pass options to toOpenAPISchema in resolver

[yy4382]

The resolver function takes in a options parameter, and passed it to both toJsonSchema and toOpenAPISchema. However these two functions actually expects two different shapes of the options. For toJsonSchema, the options is directly passed to the underlaying schema lib. But for toOpenAPISchema, it takes in { component, options }, and the latter sub-options is passed to the actual schema libs.

The test i added is a good example of the use case that requires user to pass options to underlaying lib (in this example, zod), and shows how the new interface should be used.

The current API design is far from perfect, but this is the best solution I can think of to avoid breaking changes.

[MathurAditya724]

Thank you for this, I was also thinking about this lately. Let me try to draft a new API for this, if not then we can move with this one.