fix: propagate JsonView context when resolving Page<T> schema

[Akila-1329]

Problem

When a controller method is annotated with @JSONVIEW and returns Page,
the generated OpenAPI schema ignores the JsonView and exposes all fields
of T instead of only the fields marked with that view.

Root Cause

In PageOpenAPIConverter.resolvePagedModelType(), a new AnnotatedType is
created for PagedModel but only copies the type information, dropping
the ctxAnnotations which carry the @JSONVIEW context.

Fix

Pass the original AnnotatedType to resolvePagedModelType() and copy its
ctxAnnotations onto the new AnnotatedType, preserving the JsonView context.

Test

Added test app245 which verifies that @JSONVIEW(Hello.class) on a method
returning Page correctly generates HelloWorld_Hello schema
with only the hello field.

[bnasslahsen]

Thanks @Akila-1329 for your contribution to the project!