simple cache for ROOTFile and remove cache for TDirectory

[Moelf]

fix #272
fix #269

I looked at what we're actually indexing on a ROOTFile, and found out that in the case of
reading NanoAOD, it's just indexing "Events" for ~1400 times, and everything else once e.g.
(Events/blah). So I decided to just use a naive dict like this.

In the following PRs I will add more robust tests so we can figure out why we had a LRU cache
for TDirectory and if we need one in the future, and also prevent future regression.

---

The code logic is basically rolling back to v0.10.5 but then do a naive cache dict manually

[Moelf]

@tamasgal you might want to fix the MD5 thing soon, apparently the internal API changed

• MD5 stopped working for Julia 1.11 JuliaCrypto/MD5.jl#11

[codecov]

Codecov Report

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

Files	Coverage Δ
src/bootstrap.jl	86.97% <100.00%> (-0.03%)	⬇️
src/root.jl	94.11% <93.33%> (-0.66%)	⬇️

... and 2 files with indirect coverage changes

📢 Thoughts on this report? Let us know!.

[tamasgal]

Oh, that MD5 comes out of nowhere. Thanks.

[grasph]

Hello Jerry

On my side, tt stills take >=20 s (22s) for the setup time with master (3611ee)

LazyTree display is taking a very long time (I interrupted before end)

[Moelf]

On my side, tt stills take >=20 s (22s) for the setup time with master (3611ee)

do you have a sample file with not too many events? or just point me to an open data file maybe

LazyTree display is taking a very long time (I interrupted before end)

this is expected, because reading those branches for the first time is slow, and display needs to read first basket of each branch, displayed and last basket of each branch displayed

[grasph]

Thanks for looking at this. You can find a file with 10 events in https://cernbox.cern.ch/s/Vy6Yhz47vDaYiWa

[grasph]

Hello Jerry

On my side, tt stills take >=20 s (22s) for the setup time with master (3611ee)

LazyTree display is taking a very long time (I interrupted before end)

Clarification: with v0.10.16 setup time was 120s and it was v.10.15 it was 21s. So regression for the setup time is fixed. v0.10.15 and v0.10.16 didn't have the issue with the display.

Philippe.