fix(api): wrong path for signature API

[guzmud]

Description

#257 was made targeting /api/injects/{injectId}/callback instead of /api/injects/execution/callback/{injectId}

Environment

1. OS: { e.g. macOS 14, Windows 11, Ubuntu 22.04, etc. }
2. Version: { e.g. 1.2.3 }
3. Other environment details:

Reproducible steps

Steps to create the smallest reproducible scenario:

1. { e.g. Run ... }
2. { e.g. Click ... }
3. { e.g. Error ... }

Expected output

Actual output

Additional information

[Filigran-Automation]

🤖 [AI-generated]

Hey @guzmud! 👋 Thanks a lot for opening issue #284 and for pinpointing the wrong vs. correct path so precisely — that's really helpful! 🙏

I just had a quick look and I think the description could be enhanced a little to help maintainers act on it faster. I haven't changed anything in your description — just a gentle, optional suggestion:

Area	What could help	Suggestion
## Environment	Placeholders left in ({ e.g. macOS 14 }, { e.g. 1.2.3 })	Fill in the client-python version where the wrong path is hit
## Reproducible steps	Template placeholders ({ e.g. Run ... })	Add the minimal steps that trigger the call to the wrong endpoint
## Expected output / ## Actual output	Both empty	Note that the request should hit /api/injects/execution/callback/{injectId} but currently goes to /api/injects/{injectId}/callback (e.g. resulting status/error)

💡 If helpful, the contribution conventions and the bug issue template walk through what to include.

No rush at all — thanks again for contributing to OpenAEV! 🚀