KAFKA-10798; Ensure response is delayed for failed SASL authentication with connection close delay

[rajinisivaram]

Committer Checklist (excluded from commit message)

• Verify design and implementation
• Verify test coverage and CI build status
• Verify documentation (including upgrade notes)

[omkreddy]

@rajinisivaram Thanks for the PR. LGTM.

[rajinisivaram]

@omkreddy Thanks for the review, merging to trunk.

[efajunk]

Hello!
I'm not sure that the reason is still here, but we have exactly SASL authentication and the delay "still" doesn't work.
Our Kafka version is 3.3. We see in logs that it's definitely applied, but with no effect(

2023-04-17 14:58:36,322 INFO KafkaConfig values: 
...
	connection.failed.authentication.delay.ms = 1000
...

Log shows nonstop authorization attempts. One per 10 milliseconds (log ex below). Errors rate for the same topic is kept at the 1-2k per minute.

2023-04-17 15:02:45,266 INFO Principal = User:same_user is Denied Operation = Describe from host = x.x.x.x(same_ip) on resource = Topic:LITERAL:same_topic for request = Metadata with resourceRefCount = 1 (kafka.authorizer.logger) [handler-0]
2023-04-17 15:02:45,268 INFO Principal = User:same_user is Denied Operation = Describe from host = x.x.x.x(same_ip) on resource = Topic:LITERAL:same_topic for request = Metadata with resourceRefCount = 1 (kafka.authorizer.logger) [handler-3]
2023-04-17 15:02:45,268 INFO Principal = User:same_user is Denied Operation = Describe from host = x.x.x.x(same_ip) on resource = Topic:LITERAL:same_topic for request = Metadata with resourceRefCount = 1 (kafka.authorizer.logger) [handler-10]
2023-04-17 15:02:45,269 INFO Principal = User:same_user is Denied Operation = Describe from host = x.x.x.x(same_ip) on resource = Topic:LITERAL:same_topic for request = Metadata with resourceRefCount = 1 (kafka.authorizer.logger) [handler-11]

Maybe there is still another config to make the delay work?