Enable dynamic creation of storage clients based on bucket type and specified protocol

[abhishek10004]

Enable dynamic creation of storage clients based on bucket type and specified protocol

Reason for not using mutex in getClient:
Multiple clients can be created in dynamic mounting case only. But in this case, the root dir will actually be a base_dir & we take a lock before calling LookUpChild for base_dir. So, this will ensure that call to BucketHandle (which means calls to getClient) will be serialized.

Reason for not adding a new config EnableBidiConfig in StorageClientConfig (& instead passing a separate parameter for bidi config while creating grpc client):
This config is created from the user provided config at the start (& should reflect that) and I would not like to keep a transient field to it (i.e. would not like to keep a field which has to be set every time before grpc client creation happens and does not serve any other purpose apart from reducing an extra parameter to grpc client creation call).

Testing: Manually tested mounting/listing/reading on flat, hns and zb bucket with this change using dynamic mounting (with both grpc as well as http)

[codecov]

Codecov Report

Attention: Patch coverage is 72.05882% with 19 lines in your changes missing coverage. Please review.

Project coverage is 75.69%. Comparing base (088fee5) to head (97deb8a).
Report is 5 commits behind head on master.

Files with missing lines	Patch %	Lines
internal/storage/storage_handle.go	69.84%	13 Missing and 6 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2922      +/-   ##
==========================================
- Coverage   75.83%   75.69%   -0.15%     
==========================================
  Files         125      125              
  Lines       17624    17641      +17     
==========================================
- Hits        13366    13353      -13     
- Misses       3701     3728      +27     
- Partials      557      560       +3     

Flag	Coverage Δ
unittests	75.69% <72.05%> (-0.15%)	⬇️

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

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.