Information date switches 1 day

[DzMakatun]

Describe the bug

In the monitoring tab in Menas informations dates are shown as +1 day from the actual date.

To Reproduce

Compare the displayed information dates to the original records in the DB
Example dataset: spear_sovereignindicators

Expected behavior

A clear and concise description of what you expected to happen.

Screenshots

Additional context

The older Enceladus version, when Monitoring was implemented, was storing informationDate as a date string only. In the current version it includes default time of 23:59:59.590 which is 10 milliseconds before the midnight. Also, the timezone is not specified. The date gets switched, probably when casting the string to datetime object or adjusting for browser timezone. Further investigation is needed.

Release notes

Fixed incorrect info date display in monitoring UI.

[DzMakatun]

The root of the issue:
the infodate is stored without a timezone in mongo. For monitoring we to cast it to ISODate in mongo quiry to make it searchable. but when local time differs from GMT it gets shifted 1 day.

controlMeasure.metadata.informationDate
From user
controlMeasure.metadata.additionalInfo.enceladus_info_date
From spark-job

Should be same. But controlMeasure.metadata.informationDate format is not enforced at all.
Second's format should be enforced I think

Proposed solution:
keep mongo queries the same for internal processing but display the original enceladus_info_date string in the UI.

[DzMakatun]

Checked existence of controlMeasure.metadata.additionalInfo.enceladus_info_date
in run docs

Using:
db.getCollection('run_v1').find({"controlMeasure.metadata.additionalInfo.enceladus_info_date": null},{"controlMeasure.metadata.additionalInfo.std_enceladus_version":1}).sort({"controlMeasure.metadata.additionalInfo.std_enceladus_version":-1}).limit(30)

Conclusion: all runs since 0.4.180 has the new attribute included. It is safe to switch.