[TTAHUB-3036] Filter out TR goals from similarity api

[AdamAdHocTeam]

Description of change

We want to exclude TR goals for the similarity API. This change does two things:

• Prevents goals with a createdVia of 'tr' from coming back via the API.
• Delete's any TR goals that currently have merge suggestions but are NOT merged.

As of writing this there are currently no TR goals that have been merged.

How to test

• Review the code.
• Run the test.http test called '### given a text, compute similarities for this recipient' for a TR goal and recipient (nothing should come back).
• Run the same test in the above step for a valid createdVia it should return results.
• Run the migration make sure we no longer have any 'GoalSimilarityGroups' or 'GoalSimilarityGroupGoals' for non-merged TR goals.

Issue(s)

• https://jira.acf.gov/browse/TTAHUB-3036

Checklists

Every PR

• Meets issue criteria
• JIRA ticket status updated
• Code is meaningfully tested
• Meets accessibility standards (WCAG 2.1 Levels A, AA)
• API Documentation updated
• Boundary diagram updated
• Logical Data Model updated
• Architectural Decision Records written for major infrastructure decisions
• UI review complete

Before merge to main

• OHS demo complete
• Ready to create production PR

Production Deploy

• Staging smoke test completed

After merge/deploy

• Update JIRA ticket status

[thewatermethod]

You could just increment the version number of the goal similarity groups instead of doing this, that is what it's for

[AdamAdHocTeam]

oops ok Ill just up the version instead.