Improve efficiency of repository and integrity meta analysis

[nscuro]

Description

Improves efficiency of repository and integrity meta analysis.

• Removes "preparation" logic of IntegrityMetaComponent records in BomUploadProcessingTask. Preparing records one-by-one is too resource-intensive, but doing it in batches has a too high potential for deadlocks since the table is written to by many threads in parallel.
• Removes the differentiation between fetching latest version, fetching integrity metadata, and fetching both. The amount of bookkeeping necessary to enable this sadly makes the entire undertaking inefficient.
• Refactors RepositoryMetaResultProcessor to consume records in batches. Since incoming records are keyed by PURL coordinates, we can safely perform batch operations in the database without the risk of running into deadlocks.

Warning

This is a breaking change:

• /api/v1/component/integritymetadata is removed
• /api/v1/component/integritycheckstatus is removed

The removed endpoints are not used by the frontend. Integrity data is already part of the /api/v1/component response, making dedicated endpoints not a requirement right now.

Addressed Issue

Closes DependencyTrack/hyades#1306

Additional Details

Hyades PR: DependencyTrack/hyades#1446

Checklist

• I have read and understand the contributing guidelines
• This PR fixes a defect, and I have provided tests to verify that the fix is effective
• This PR implements an enhancement, and I have provided tests to verify that it works as intended
• This PR introduces changes to the database model, and I have updated the migration changelog accordingly
• This PR introduces new or alters existing behavior, and I have updated the documentation accordingly

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ -0.22% (target: -1.00%)	✅ 71.15% (target: 70.00%)

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (c5dcf4d)	22242	18392	82.69%
Head commit (acc711d)	21974 (-268)	18122 (-270)	82.47% (-0.22%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#846)	260	185	71.15%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}

[nscuro]

Trying to figure out how we can still populate the REPOSITORY_META_COMPONENT.LAST_CHECK and INTEGRITY_META_COMPONENT.LAST_FETCH columns, without spamming the database with pointless UPDATE queries.

Ideally we wouldn't change any rows if their content didn't meaningfully change, but if we don't do it we can't keep LAST_CHECK and LAST_FETCH accurate.