Ensure vulnerability read creations associate the record with the vulnerability tracked context

Requirements

All locations that create vulnerability reads will need to be updated to ensure that the vulnerability read is appropriately updated with the security_project_tracked_context_id of the related vulnerability record when it is changed.

This issue may be incidentally resolved in the process of implementing updates to the services elsewhere, but we need to ensure that all vulnerability_reads are being configured with the appropriate context id.

Ideally there will be some nicely unified services that make it straightforward to integrate this behaviour as a result of the migration away from the database trigger functionality.

Vulnerability Reads Create Scenarios:

• Vulnerability reports ingestion: handled in !213439 (merged)
• CVS ingestion: handled in !213439 (merged)
• Starboard Vulnerability Creation
  • module: Vulnerabilities::StarboardVulnerabilityCreateService
• Manual Vulnerability Creation
  • module: Vulnerabilities::ManuallyCreateService
• Created from Security Findings/API
  • module: Vulnerabilities::CreateService