fix(event_handler): revert regression when validating response

[leandrodamascena]

Issue number: #6216

Summary

Changes

This PR addresses a regression that was introduced by PR #6119. The regression impacts the validation of responses specifically when utilizing the Response object with specific data type.

User experience

The code bellow will fail with this regression

from aws_lambda_powertools.event_handler import APIGatewayRestResolver, Response
import json
from pydantic import BaseModel
from typing import List

app = APIGatewayRestResolver(enable_validation=True)

class StatusGroup(BaseModel):
    count: int
    status: str   

def lambda_handler(event, context):
    return app.resolve(event,context)

@app.get("/status", 
        summary="status",
        description="count",
        response_description="status count",
        responses={
            200: {"description": "status count"}
        }
    )
def status( requests:List[str]) -> List[StatusGroup]:
    response = [{"status":"initial","count":1},{"status":"done","count":1}]
    return Response(200, body=json.dumps(response))

def main():
    event = {
        "path": "/status",
        "httpMethod": "GET",
        "requestContext": {"requestId": "227b78aa-779d-47d4-a48e-ce62120393b8"}, 
        "body": '["1","2","3"]'
    }
    response = lambda_handler(event,None)
    print(json.dumps(response,sort_keys=True, indent=4, default=str))

if __name__ == "__main__":
    main()

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.30%. Comparing base (76b4d8f) to head (83b8e01).
Report is 1 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #6234      +/-   ##
===========================================
+ Coverage    96.28%   96.30%   +0.01%     
===========================================
  Files          240      240              
  Lines        11572    11572              
  Branches       858      858              
===========================================
+ Hits         11142    11144       +2     
+ Misses         337      336       -1     
+ Partials        93       92       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.