Optional detailed report on the BasicCCDBManager cache

[shahor02]

@ktf @jgrosseo this PR extends the report of the BasicCCDBManager statistics to the same detailed level as produced by the DPL CCDBHelper. One should explicitly call BasicCCDBManager::instance().report(true) to have the extended report, by default only the old summary string is printed:

auto& cc = o2::ccdb::BasicCCDBManager::instance();
cc.get<o2::parameters::GRPECSObject>("GLO/Config/GRPECS");
cc.setTimestamp(17021636063139);
cc.get<o2::parameters::GRPECSObject>("GLO/Config/GRPECS"); // fails as the timestamp is bogus;
cc.setTimestamp(1702163606313);
cc.get<o2::parameters::GRPECSObject>("GLO/Config/GRPECS");
cc.get<o2::parameters::GRPECSObject>("GLO/Config/GRPECS");
cc.get<o2::parameters::GRPECSObject>("GLO/Config/GRPECS");
cc.get<TGeoManager>("GLO/Config/Geometry");
cc.get<TGeoManager>("GLO/Config/Geometry");

cc.report(true);

[INFO] CCDBManager summary: 7 queries for 2 objects, 3 good fetches (and 0 failed ones) in 4,009 ms, instance: alicrs02-1702170696-lhV1VF
[INFO] CCDB cache miss/hit/failures
[INFO]   GLO/Config/Geometry: 1/1/0 (1883722-1883722 bytes)
[INFO]   GLO/Config/GRPECS: 2/2/1 (1809-1820 bytes)

Let me know what exactly you want to send to the monitoring, I will prepare a getter for corresponding Metric.

[jgrosseo]

Thanks. This looks very good.
I only had the plan to harvest the total transferred bytes (what are the ranges actually?)
Nevertheless, as you have it by object, you could send all that info to monitoring per object (if someone else needs that) and I can do the aggregation on my side. I let @ktf in which structure to send this back.

[shahor02]

The printout corresponds to what @ktf did for the DPL fetcher (+ number of failures per object, since the BasicCCDBManager is allowed to go over them): range is the min and max size of the object for given path.

I am afraid sending per object info to monitoring will require 1 metric per object, not sure if it is not too much, perhaps @ktf may comment.

[shahor02]

@jgrosseo I've added a getter

size_t o2::ccdb::BasicCCDBManager::getFetchedSize();

Let me know if this is enough, then I'll merge this.

[alibuild]

Error while checking build/O2/fullCI for ad12117 at 2023-12-16 09:58:

## sw/BUILD/O2-latest/log
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'


## sw/BUILD/QualityControl-latest/log
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'


## sw/BUILD/O2Physics-latest/log
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'
c++: error: unrecognized command-line option '--rtlib=compiler-rt'


## sw/BUILD/O2-full-system-test-latest/log
command /sw/slc8_x86-64/O2/12430-slc8_x86-64-local1/prodtests/full-system-test/dpl-workflow.sh had nonzero exit code 1


## sw/BUILD/o2checkcode-latest/log
--
========== List of errors found ==========
++ GRERR=0
++ grep -v clang-diagnostic-error error-log.txt
++ grep ' error:'
++ GRERR=1
++ [[ 1 == 0 ]]
++ mkdir -p /sw/INSTALLROOT/2f7505c60144794742d7a053de073f7ebc17fe39/slc8_x86-64/o2checkcode/1.0-local512/etc/modulefiles
++ cat
--

Full log here.

[shahor02]

@jgrosseo merging this, if extra methods are needed, let me know, will do in other PR.