Update cve status options and apply updates across test fixtures

[mtruj013]

Done

• Updated cve statuses to replace "active" with "in-progress"

QA

• Check out this feature branch
• Run the site using the command dotrun
  • If you get errors in this step, stop and restart the docker container then try dotrun again
• View the site locally in your web browser at: http://0.0.0.0:8030/security/cves.json
• See that the endpoint returns without error and that the default CVE status is "in-progress" instead of "active"

Issue / Card

Fixes https://warthogs.atlassian.net/browse/WD-15029

[mtruj013]

Bug to be fixed: Running migration is throwing the following error psycopg2.errors.InvalidTextRepresentation: invalid input value for enum cve_statuses: "active"

[petesfrench]

What I have done:

• unzipped 'sample-security-data.sql.gz' and updated 'active' to 'in-progress'
• added db as an import as the 'generate-sample-security-data.py' was complaining
• removed enum as a sqlalchemy import to appease the linter gods

[petesfrench]

LGTM, just a question to clarify something. Might be my lack on context but maybe a more detailed comment would help future devs

[petesfrench]

What is the default status? in progress?