fix(openapi): correct response validation for falsy objects

[amin-farjadi]

Issue number: closes #5887, #6216

Summary

Fix openapi response validation behaviour on Falsy return objects.

Changes

in openapi_validation.py, OpenAPIResponseValidationMiddleware class:

• behaviour of _handle_response method modified
• behaviour of _serialize_response method modified
• _serialize_response method renamed to _serialize_response_with_validation

in test_openapi_validation_middleware.py:

• remove the skip from test_validation_error_none_returned_non_optional_type to cover issue Bug: Open API Validation not validating response serialization when body is Falsy. #5887
• added test_validation_error_different_list_returned_non_optional_type and test_validate_list_response to cover Bug: Upgrade to 3.7.0 breaks List response validation in APIGatewayRestResolver #6216

in test_http_resolver_pydantic.py:

• test_async_handler_with_validation marked to skip due to issue Bug(HttpResolverLocal): OpenAPIResponseValidationMiddleware is not working as intended #7981

User experience

Now Falsy response will be validated againt the OpenAPI return field (is there is any).

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[powertools-for-aws-oss-automation]

Not all issues are linked correctly.

Please link each issue to the PR either manually or using a closing keyword in the format fixes #<issue-number> format.

If mentioning more than one issue, separate them with commas: i.e. fixes #<issue-number-1>, closes #<issue-number-2>.