Improve clarity of "Public At" input field to prevent accidental publishing d/t "scheduling" assumption

[openmorse]

The CVE schema field "datePublic" is intended to record the date (if known) that the vulnerability may have become public in the past, not in the future:

"datePublic": { "$ref": "#/definitions/timestamp", "description": "If known, the date/time the vulnerability was disclosed publicly." },

There is no mechanism in CVE Services to "schedule" a record for future publication. Some users have misunderstood this and published their records early by accident after setting a future date in Vulnogram's "Public At" input field:

Suggest either renaming the GUI input field or adding a note or otherwise making it more clear that it does not provide scheduling of record publishing.

[ElectricNroff]

Setting a future date in Vulnogram's "Public At" input field will no longer publish the CVE Record because of this CVE Services change: CVEProject/cve-services#1097 from https://github.com/CVEProject/cve-services/projects/59

The current behavior of Vulnogram, with the CVE Services test instance, is that the future date leads to this error window:

BAD_INPUT

Parameters were invalid
body/ cnaContainer.datePublic: datePublic cannot be a future date

and the CVE Record is not published. The error message will be similar for any client because the CVE Services server refuses the API call:

HTTP/1.1 400 Bad Request

{"error":"BAD_INPUT","message":"Parameters were invalid","details":[{"msg":"datePublic cannot be a future date","param":"cnaContainer.datePublic","location":"body"}]}

This server behavior will be moved form the test instance into CVE Services production in early January 2024.