fix(server): harden tools and chatmessage route contracts

[sahil2448]

Summary

fixes : #6428

This PR removes ambiguous / route variants for handlers that require :id, and aligns route definitions with current controller expectations.
Even though normal frontend flows were already working, these route definitions were still inconsistent and could cause avoidable 412 errors for future integrations or refactors.

What changed

• Updated tools routes to require :id for id-based handlers:
  • GET /tools/:id (removed / variant for get-by-id)
  • PUT /tools/:id (removed / variant for update)
  • DELETE /tools/:id (removed / variant for delete)
• Updated chatmessage routes similarly:
  • GET /chatmessage/:id (removed / variant)
  • DELETE /chatmessage/:id (removed / variant)
• Normalized abort route to PUT /chatmessage/abort/:chatflowid/:chatid

Files changed

• packages/server/src/routes/tools/index.ts
• packages/server/src/routes/chat-messages/index.ts

Why this matters

Controllers for these handlers already require req.params.id.
Previous route setup accepted both / and /:id, which made the API contract ambiguous.
Calling / for id-required handlers could hit controller logic and fail with 412 (id not provided) instead of being clearly non-matching at the route layer.
This change makes behavior predictable and safer for future clients and tests.

Compatibility and risk

• Low risk, backend-only route-contract hardening.
• No change to controller/service business logic.
• Existing frontend usage remains compatible because UI already calls /:id endpoints.

Validation

• Verified current frontend API callers still target /:id:
  • packages/ui/src/api/tools.js
  • packages/ui/src/api/chatmessage.js
• Local commit hooks passed successfully.
• Also tested frontend side -- not giving any issue.

Checklist

• Kept existing functionality intact for current UI flows
• Limited scope to route contract cleanup
• No unrelated files included in commit

[gemini-code-assist]

Code Review

This pull request simplifies the routing logic in the chat-messages and tools modules by replacing array-based route definitions with single, parameterized paths. Specifically, it removes the optional root paths from GET, PUT, and DELETE endpoints, ensuring that these routes now explicitly require an ID or specific parameters. I have no feedback to provide as there were no review comments to evaluate.

[sahil2448]

@ maintainers, waiting for Review and Merge if this issue and PR is considerable...!