Answer
This was a confirmed gap (no built-in cleanup for the virus-scanner scan log) that has since been addressed starting from a specific Support Update — check whether your current release already includes a retention/cleanup mechanism for this table before building a custom purge job to manage its growth yourself.