pvlib.iotools.get_cams not following CAMS default timestamp convention

[ramaroesilva]

Describe the bug
pvlib.iotools.get_cams (link) provides satellite radiation estimates at different temporal scales (from 1 min to 1month). while the function allows users to define their timestamp convention through the labelparameter (i.e., if 15-min averaged datapoint at 10:00 corresponds to 9:45-10 or 10-10:45), the default assumption is not coherent with the data provider original setup.

Expected behavior
label would be right by default, rather than left.

Screenshots
From CAMS documentation:

[adriesse]

It seems ok to return data with a different default convention than cams (iotools convention?) as long as they line up correctly... do they?

[ramaroesilva]

It's not a "capital sin", but I've understood from previous discussion that pvlib aims to mimic as much as possible the original source. In addition, from my understanding (but I'm biased and with only a partial perspective, naturally) the right option is much more in agreement with conventions.

If there is a general feeling that there is no need to adapt the code, I would at least clarify this in the documentation.