[AIT] Improve test coverage for Netty involving HTTP2 edge cases

[obenkenobi]

Description

In light of a recent PR, new tests for Netty (preferably AITs) should be added that address edge cases for HTTP2 calls.

These include apps that make HTTP2 web requests and apps that use Http clients that call HTTP2 listeners within Netty. You can use a customer sample app to help build an AIT.

Acceptance Criteria

Tests need to address the following scenarios:

Http2 Web Transactions

Flipping the value of the config below should not affect wether HTTP2 web transactions are made

  netty:
    http2:
      frame_read_listener:
        start_transaction: false

Netty web transactions that uses a web client that makes calls to internal HTTP2 methods

Setting the below config to 'false' should make is so that 'unknown' transactions do not appear.

  netty:
    http2:
      frame_read_listener:
        start_transaction: false

Setting the above config to 'true' should make is so that 'unknown' transactions do appear.

[Newrelic-Boomi]

https://new-relic.atlassian.net/browse/NR-419878

[jasonjkeller]

We do have a Netty HTTP2 test app and an HTTP2 test in our AITs. These can likely just be extended to test the additional case called out in this ticket.

[sharvath-newrelic]

A couple of edge case tests for this work have been PRed. There is an ongoing issue with unexpired tokens leading to timeouts when running Micronaut integration tests, which will be an impediment to fleshing out the remaining edge case AITs (the origin of this ticket's issue was discovered via a Micronaut application using Kotlin). Doug Hilpipre will be looking into a solution over the next few weeks, at which point the remaining work should be considered.

[sharvath-newrelic]

We have fixes in the pipeline for the Micronaut unexpired tokens issue. This task will be revisited after those fixes are merged.