404 page in Translations after removing a Term

[Alfro]

Describe the bug
I get a 404 page after removing a Term from traduora and navigating to a locale's Translations.

To Reproduce
Steps to reproduce the behavior:

1. Create empty project
2. Create one or more Terms
3. Create one or more new Locales
4. Remove one of the Terms
5. Navigate to Translations ->

Expected behavior
The unremoved terms are listed and ready to add a translation

Actual behavior
I get redirected to the 404 page.

Screenshots
If applicable, add screenshots to help explain your problem.

** Environment (please complete the following information):**
Running dockers locally:

• Branch: develop
• Commit: dab7800

Tested on:

• Device: Web

• OS: Linux-based

• Browser: Firefox

• Version: 140

Additional context
No logs that I could see. Docker logs only shows that the request responded with a 404:

traduora  | 172.39.3.1 - GET /api/v1/projects/3a5daf55-165f-41e4-be0f-d922587083d9/translations/en_AU HTTP/1.1 404 83 - 3.770 ms

Videos showing the steps to reproduce the bug with different combinations of actions:
https://github.com/user-attachments/assets/1c57bc24-4218-4900-ade3-61f27ec45e00
https://github.com/user-attachments/assets/4c97ee38-9c6b-47b1-a52e-f201ebdd5453
https://github.com/user-attachments/assets/c3c1a3cb-a2c5-40b1-9ff7-cb7f8e91fc6e

[Alfro]

Looking at the DB, it looks like the removed Term still has an associated translation that wasn't removed:

sqlite> select id,value,project_id from term where project_id = '90ccc3e8-73e3-4e67-904f-c2c5cd259d59';
22e63679-18bf-4997-b476-a57dee1c1e50|Term2|90ccc3e8-73e3-4e67-904f-c2c5cd259d59

sqlite> select term_id,value,project_locale_id from translation tr join project_locale pl on pl.id = tr.project_locale_id and project_id = '90ccc3e8-73e3-4e67-904f-c2c5cd259d59';
6aa0b8b1-cab8-48ac-b2bc-d2905a93c9ca|Translated Term1|a54e61e4-d2d4-4cda-a04b-154767bc9f17
22e63679-18bf-4997-b476-a57dee1c1e50|Translated Term2|a54e61e4-d2d4-4cda-a04b-154767bc9f17

[Alfro]

I've tentatively opened a PR with a partial fix. It does not address the extra db rows but it will filter translations without existing terms from the endpoint's results