[fix][client] Fix concurrent lookup with properties might have different results

[BewareMyPower]

Motivation

When the lookup properties are modified, the previous pending lookup might use the modified properties for lookup.

Modifications

• Combine the properties and the topic name as the key to cache pending lookup requests.
• Return copied properties rather than the reference in ClientConfigurationData#getProperties
• Add testConcurrentLookupProperties to cover this case.

Documentation

• doc
• doc-required
• doc-not-needed
• doc-complete

Matching PR in forked repository

PR in forked repository:

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.53%. Comparing base (bbc6224) to head (8e48dc0).
Report is 566 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #23260      +/-   ##
============================================
+ Coverage     73.57%   74.53%   +0.96%     
- Complexity    32624    34292    +1668     
============================================
  Files          1877     1926      +49     
  Lines        139502   145043    +5541     
  Branches      15299    15862     +563     
============================================
+ Hits         102638   108111    +5473     
+ Misses        28908    28683     -225     
- Partials       7956     8249     +293     

Flag	Coverage Δ
inttests	27.96% <100.00%> (+3.38%)	⬆️
systests	24.63% <100.00%> (+0.31%)	⬆️
unittests	73.89% <100.00%> (+1.05%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...e/pulsar/client/impl/BinaryProtoLookupService.java	81.69% <100.00%> (-0.85%)	⬇️

... and 561 files with indirect coverage changes