Relax wording of EPSS re-population delay (#144)

The task starts a few minutes after startup and usually completes in <30s thanks to batch loading. The current "within hours" wording is overly pessimistic.

Signed-off-by: Niklas <nscuro@protonmail.com>

Author: nscuro

docs/guides/administration/migrating-from-v4.md

@@ -364,7 +364,7 @@ v4 inactive projects become `INACTIVE_SINCE = '1970-01-01 00:00:00+00'` (Unix ep
 
 v4 stored EPSS score and percentile directly on each vulnerability row.
 v5 stores EPSS in a dedicated table populated from the upstream feed.
-The migrator does not copy v4 EPSS values. v5 re-populates them at runtime within hours of first launch.
+The migrator does not copy v4 EPSS values. v5 re-populates them at runtime within minutes of first launch.
 
 ### Metrics retention