[backend] Add `auto_resolved` boolean for Vulnerabilities

Why are we doing this work?

As per #233846[design_1660094880459.png] we need to be able to filter auto-resolved Vulnerabilities

In #233846[design_1660094880459.png] (comment 2119838621) we decided it makes more sense to introduce another state instead of performing JOINs on vulnerability_state_transitions.

Implementation plan

  1. Add auto_resolved boolean column to vulnerabilities
  2. Add auto_resolved boolean columns to vulnerability_reads
  3. Update vulnerabilities trigger to copy auto_resolved column to vulnerability_reads

Note

index_vulnerabilities_on_state_case_id no longer exists so we don't need to recreate it contrary to what the enum says.

Edited by Ryan Wells