Prohibit adding dates in a wrong order

[orchestr7]

There is a simple logic of order for types of dates, for example: “introduced”, “found”, “fixed”, “disclosed”;

Obviously it cannot be fixed BEFORE found - we need to raise a warning about that.

@nulls if you have some vision on that based on the COSV format - welcome to add it here :)

[nulls]

I guess the following fields can be calculated automatically and cannot be updated by UI:

• publised -- when vulnerability is created
• modified -- when vulnerability is updated last time
• withdrawn -- when vulnerability is removed from our system