Change owasp_top_10 column default to int on vulnerability_reads

What does this MR do and why?

Change owasp_top_10 column default from null to int on vulnerability_reads

We have identified changing default to -1 efficiently uses the index as noted in #473748 (closed)

This is the 1st MR from the implementation plan.

Related to #473748 (closed)

Database

1. Migration up > bundle exec rake db:migrate:up:main VERSION=20240805183223

main: == [advisory_lock_connection] object_id: 127760, pg_backend_pid: 53759
main: == 20240805183223 ChangeVulnerabilityReadsOwaspTop10Default: migrating ========
main: -- change_column_default("vulnerability_reads", "owasp_top_10", {:from=>nil, :to=>-1})
main:    -> 0.0209s
main: == 20240805183223 ChangeVulnerabilityReadsOwaspTop10Default: migrated (0.0245s)

main: == [advisory_lock_connection] object_id: 127760, pg_backend_pid: 53759

2. Migration down > bundle exec rake db:migrate:down:main VERSION=20240805183223

main: == [advisory_lock_connection] object_id: 127720, pg_backend_pid: 54197
main: == 20240805183223 ChangeVulnerabilityReadsOwaspTop10Default: reverting ========
main: -- change_column_default("vulnerability_reads", "owasp_top_10", {:from=>-1, :to=>nil})
main:    -> 0.0149s
main: == 20240805183223 ChangeVulnerabilityReadsOwaspTop10Default: reverted (0.0193s)

main: == [advisory_lock_connection] object_id: 127720, pg_backend_pid: 54197

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.