no need for segment locks during segment preloading

[klsince]

Taking segmentLock during segment preloading is not needed and in fact could cause deadlock when other tables trying to take the same segmentLock due to hash collision

[codecov-commenter]

Codecov Report

Attention: 6 lines in your changes are missing coverage. Please review.

Comparison is base (c57117a) 0.00% compared to head (4342914) 61.63%.
Report is 3 commits behind head on master.

Files	Patch %	Lines
...cal/upsert/BasePartitionUpsertMetadataManager.java	50.00%	3 Missing and 2 partials ⚠️
...t/local/upsert/BaseTableUpsertMetadataManager.java	0.00%	1 Missing ⚠️

Additional details and impacted files

@@              Coverage Diff              @@
##             master   #12077       +/-   ##
=============================================
+ Coverage      0.00%   61.63%   +61.62%     
- Complexity        6     1153     +1147     
=============================================
  Files          2314     2389       +75     
  Lines        126078   129817     +3739     
  Branches      19524    20082      +558     
=============================================
+ Hits              6    80010    +80004     
+ Misses       126072    43978    -82094     
- Partials          0     5829     +5829     

Flag	Coverage Δ
custom-integration1	<0.01% <0.00%> (ø)
integration	<0.01% <0.00%> (ø)
integration1	<0.01% <0.00%> (?)
integration2	0.00% <0.00%> (?)
java-11	61.56% <45.45%> (+61.56%)	⬆️
java-21	61.51% <45.45%> (+61.50%)	⬆️
skip-bytebuffers-false	61.61% <45.45%> (?)
skip-bytebuffers-true	61.48% <45.45%> (?)
temurin	61.63% <45.45%> (+61.62%)	⬆️
unittests	61.62% <45.45%> (?)
unittests1	46.90% <0.00%> (?)
unittests2	27.61% <45.45%> (?)

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.