fix(sideloading): avoid the expected data deletion during SST side loading

[ltagliamonte-dd]

Hello folks,
we think we may experiencing data deletion during expensive (thousand of sst files) sst side loading operations.
what we think it is happening is:

• T1 - load data CF
• T2 - auto compactions runs which deletes the data as keys on the metadata CF are not yet loaded
• T3 - load metadata CF

for this reason we would love to switch the sst ingestion logic to use IngestExternalFiles that should take care of sideloading all files from different CF atomically.

[ltagliamonte-dd]

@aleksraiden would you mind run the CI for this so i can test a nightly build?

[ltagliamonte]

@git-hulk thanks for the CI run, the failures look like flaky isn't it?
Where can I find the nightly build for latest Sha?

[git-hulk]

@ltagliamonte-dd Yes, this test failure is not related to this PR.

Where can I find the nightly build for latest SHA?

The Docker nightly build can only get after merging the PR. But you can also build it manually and push it to your own Docker repository if you're in a hurry to have a test.

[ltagliamonte]

Thank you @git-hulk , do you mind reviewing and maybe ping someone else so we can get this merged?
It should be pretty straightforward we aren't changing the behavior and the test pass.
Thanks!

[sonarqubecloud]

Quality Gate failed

Failed conditions
0.0% Coverage on New Code (required ≥ 50%)

See analysis details on SonarQube Cloud