DPL CCDB: handle the Cache-Valid-Until header

[ktf]

DPL CCDB: handle the Cache-Valid-Until header

This will not recheck the etag and consider the cache valid until
the timestamp in milliseconds in the Cache-Valid-Until is not passed
by the data timestamp.

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass
async-2023-pp-apass1
async-2022-pp-apass6
async-2022-pp-apass4
async-mc
async-data

[ktf]

@costing @shahor02 attempt at supporting Cache-Valid-Until header in the CCDB Reply. One thing it's not clear to me is the unit of Cache-Valid-Until. Is it milliseconds?

[shahor02]

It appears that this "Cache-Valid-Until" is provided not at the 1st query (with empty etag) and at the 1st query with valid etag (actually at the 2nd one, see my email to @costing ).
So, there is no point in its caching here, instead should be cached as done here

AliceO2/Framework/CCDBSupport/src/CCDBHelpers.cxx

Line 265 in 956b267

helper->mapURL2UUID[path].cacheValidUntil = headers["Cache-Valid-Until"].empty() ? 0 : std::stoul(headers["Cache-Valid-Until"]);

and also here

AliceO2/Framework/CCDBSupport/src/CCDBHelpers.cxx

Line 275 in 956b267

}

as

else {
  helper->mapURL2UUID[path].cacheValidUntil = headers["Cache-Valid-Until"].empty() ? 0 : std::stoul(headers["Cache-Valid-Until"]);
}

[ktf]

@shahor02 updated.

[ktf]

Passes the full system test.