feat: add safeBrowsingExpiry column to urls table

[dcshzj]

Problem

What problem are you trying to solve? What issue does this close?

We need to support the caching of the safe browsing scan results for at least 24 hours.

Solution

How did you solve the problem?

Features:

• Add a new safeBrowsingExpiry column to the urls table to support storing of the safe browsing scan result's expiry date.
  • This date represents the time in which no further safe browsing scanning is required.
  • The duration will be decided later by the producer of this information, so there is flexibility in determining when a scan result expires.

Tests

What tests should be run to confirm functionality?

• Run the DB migration to add the safeBrowsingExpiry column. Verify that the new column appears in the urls table.
• Create a new link, verify that link creation still works as intended.
• Edit the new link you have created, verify that link editing still works as intended.

Deploy Notes

Notes regarding deployment of the contained body of work. These should note any
new dependencies, new scripts, etc.

• Run DB migration to add the safeBrowsingExpiry column.

[seaerchin]

1 comment, could we also run this on staging (technically edge) to ensure that it's working properly?

i think might be hard to check manually so there's some value in having unit tests here to make sure that we rescan past 24 hours