AWS Lambda ignores console log format on requests

[ghost]

Describe the bug

Running a natively compiled quarkus app with aws-lambda and rest-easy-reactive extensions, with aws provided base image for custom runtimes.

Application logs initially use console format pattern on startup, but as soon as a request is received, the format completely changes.

Expected behavior

The configured console log format is applied to all log events.

Actual behavior

A completely different, presumably default, log format is utilized.

How to Reproduce?

1. Create quarkus app with amazon-lambda-rest and resteasy-reactive-jackson extensions.
2. Configure custom console format using "quarkus.log.console.format"
3. Compile natively using container build.
4. Build docker image using aws provided base image for custom runtimes (https://gallery.ecr.aws/lambda/provided)
5. Deploy to aws.
6. Make a request.
7. Check cloudwatch logs.

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.16.3

Build tool (ie. output of mvnw --version or gradlew --version)

maven 3.8.5

Additional information

No response

[quarkus-bot]

/cc @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda)