Optimize authorization by caching authorization results

[BewareMyPower]

Motivation

To follow Kafka's behavior, KoP also performs authorization for each PRODUCE or FETCH request. If the custom authorization provider is slow to authorize produce or consume permissions, the performance will be impacted.

Modifications

Introduce caches for authorization:

• PRODUCE: (topic, role) -> result
• FETCH: (topic, role, group) -> result;

Add SlowAuthorizationTest to verify the producer and consumer won't be affected significantly by slow authorization.

Introduce two configs to configure the cache policy so that revoke permission can work:

• kopAuthorizationCacheRefreshMs: the refresh timeout
• kopAuthorizationCacheMaxCountPerConnection: the max cache size

Documentation

Check the box below.

Need to update docs?

• [ ] doc-required

  (If you need help on updating docs, create a doc issue)

• [x] no-need-doc

  (Please explain why)

• [ ] doc

  (If this PR contains doc changes)

[codecov[bot]]

Codecov Report

Merging #1999 (9ba3925) into master (5193592) will increase coverage by 0.03%. The diff coverage is 25.00%.

@@             Coverage Diff              @@
##             master    #1999      +/-   ##
============================================
+ Coverage     17.03%   17.06%   +0.03%     
- Complexity      727      731       +4     
============================================
  Files           191      191              
  Lines         14251    14277      +26     
  Branches       1337     1340       +3     
============================================
+ Hits           2428     2437       +9     
- Misses        11646    11663      +17     
  Partials        177      177              

Files Changed	Coverage Δ
...andlers/kop/security/auth/SimpleAclAuthorizer.java	0.00% <0.00%> (ø)
...pulsar/handlers/kop/KafkaServiceConfiguration.java	76.34% <70.00%> (-0.37%)	:arrow_down:

... and 1 file with indirect coverage changes

[BewareMyPower]

@Demogorgon314 Done.