Fix specs - column in db but related code reverted

What does this MR do and why?

It fixes failing specs.

This was introduced do to a revert MR: Revert "Merge branch '388156-read-vuln-custom-r... (!120415 - merged)

The MR reverted code, but the column introduced by the original change remained in the db which caused the failing specs

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

gitlab-org/quality/engineering-productivity/master-broken-incidents#1699 (closed)