Updated Schema Validator to support openapi 3.1.0

[tanyamadaan]

This PR introduces modifications to the validation layer of the protocol server to enhance its OpenAPI validation capabilities, specifically targeting OpenAPI 3.1.0 specifications. Key changes include:

Package Update:

• Added openapi-backend version 5.11.0 to package.json. This library was chosen as an alternative to express-openapi-validator due to its limitations in handling certain validation keywords, such as contains, introduced in OpenAPI 3.1.0.

Migration to openapi-backend:

• The validation middleware has been completely refactored to replace express-openapi-validator, which could not fully support OpenAPI 3.1.0 schemas, even with the latest alpha releases.

• A custom middleware has been developed using openapi-backend to handle request validations in a manner consistent with the previous behavior of express-openapi-validator. This custom middleware ensures that validation errors are caught and managed properly, while also allowing validated requests to pass through to subsequent middleware.

Redis Utility Update:

• Updated the setWithExpiry method in the Redis utility to include a fallback mechanism for setting the expiry time. The updated logic ensures that if the provided expiry is not a positive integer, it defaults to 400 seconds:

[vbabuEM]

Hello ABee, @em-abee ,
Tanya from ONDC has raised a PR for making Protocol Server OpenAPI 3.1 compatible.
Please have a look. The following things stands out in my mind

1. Someone might have to do an indepth check of the older library to see the additional tasks it was doing during run (I think Rahul had done it sometime). We have to ensure (either by code walkthrough or test) that this new library also does those.
2. Adding this should not regress on the latency optimization the team had done with ONest support. Please ensure that it is thoroughly tested on that front before integrating.

Having said that, please prioritize this as it might be required for the ONDC winroom.

Thanks with regards,
Venkatesh

cc @tanyamadaan , @em-abee , @shreyvishal , @faizmagic , @rahul-eminds , @binrange

[em-abee]

Hi @tanyamadaan,

May I know the base branch details, is it for your internal use?
Also, we have fixed it conditionally for 3.1.0, see if this is helpful.
#233

Thanks!