Sentinel L2A product has incorrect bounds

For example, this is the bounding box stored in bbox for tile 10SGG at timestamp 2016-05-05T19:04:02.027000Z and id S2A_MSIL2A_20160505T190402_R113_T10SGG_20210211T085211.

But this is what the tile actually contains:

For tile 10SGG there are several more of these cases. More examples are:

S2A_MSIL2A_20160714T184922_R113_T10SGG_20210212T043726
S2A_MSIL2A_20160624T184922_R113_T10SGG_20210211T224812
S2A_MSIL2A_20160614T190352_R113_T10SGG_20210211T193819
S2A_MSIL2A_20160604T184922_R113_T10SGG_20210211T163042
S2A_MSIL2A_20160525T190352_R113_T10SGG_20210211T141725
S2A_MSIL2A_20160515T184922_R113_T10SGG_20210211T113732
S2A_MSIL2A_20160505T190402_R113_T10SGG_20210211T085211
S2A_MSIL2A_20160415T190352_R113_T10SGG_20210211T040941
S2A_MSIL2A_20160405T190352_R113_T10SGG_20210211T015225
S2A_MSIL2A_20160326T185252_R113_T10SGG_20210528T193911
S2A_MSIL2A_20160306T190352_R113_T10SGG_20210528T112222
S2A_MSIL2A_20160215T190352_R113_T10SGG_20210528T070200
S2A_MSIL2A_20160205T190342_R113_T10SGG_20210528T030140
S2A_MSIL2A_20160126T185642_R113_T10SGG_20210527T232223
S2A_MSIL2A_20160116T190342_R113_T10SGG_20210527T184113
S2A_MSIL2A_20160106T190352_R113_T10SGG_20210527T104143
S2A_MSIL2A_20151227T185812_R113_T10SGG_20210526T202139
S2A_MSIL2A_20151217T190352_R113_T10SGG_20210526T062535

This is also not the only sentinel tile affected.

Start by inspecting the stored bbox metadata for the listed Sentinel L2A product IDs and comparing it with the actual tile coverage shown in the issue. Done means identifying the source of the incorrect bounds and correcting the affected Sentinel tiles, including cases beyond tile 10SGG.