Use Built-in Java HTTP Server instead of Jetty 11

[sdelamo]

Jetty 11 has a CVE. This pull request removes the usage of Jetty 11 and replaces it with the built-in Java HTTP Server support introduced in servlet-core.

Jetty 12 Handler uses org.eclipse.jetty.server.Request instead of jakarta.servlet.http.HttpServletRequest. org.eclipse.jetty.server.Request no longer implements HttpServletRequest. Because of that, to get rid of Jetty 11, we had two options: rewrite to Jetty 12 or migrate AwsApiProxyTestServer to use the Java Built-in HTTP Server and remove the usage of Jetty.

I gone the path of using the built-in HTTP Server. There are several classes introduced in this PR which I think should be in micronaut core.

[sdelamo]

@yawkat @graemerocher can we merge this?

[yawkat]

No, I want to figure out the octet thing first

[yawkat]

@sdelamo not sure why we use the mime encoder here, i couldnt find any docs requiring it

micronaut-aws/function-aws-api-proxy/src/main/java/io/micronaut/function/aws/proxy/payload2/APIGatewayV2HTTPResponseServletResponse.java

Line 53 in e18f645

.withBody(Base64.getMimeEncoder().encodeToString(body.toByteArray()));

[sonarqubecloud]

Quality Gate failed

Failed conditions
1 New Critical Issues (required ≤ 0)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE