fix(logs): handle non-string values in search to prevent runtime crash

[Tanmay-008]

Summary

The LogsPage component crashes at runtime when the backend sends a log with msg, traceId, or step that is not a string. Since the UI calls .toLowerCase() during filtering, any non-string value (null, number, object, undefined) immediately triggers a TypeError.

This PR normalizes these fields to empty strings before applying .toLowerCase(), ensuring the filtering logic never crashes even when the backend sends unexpected data types.

Related Issues

Fixes #992

Type of Change

• [x] Bug fix
• [ ] New feature
• [ ] Breaking change
• [ ] Refactor
• [ ] Other (please describe):

Checklist

• [x] I have read the CONTRIBUTING.md
• [x] My code follows the code style of this project
• [ ] I have added tests where applicable
• [ ] I have tested my changes locally
• [ ] I have linked relevant issues
• [ ] I have added screenshots for UI changes (if applicable)

Screenshots (if applicable)

Additional Context

[vercel[bot]]

Someone is attempting to deploy a commit to the motia Team on Vercel.

A member of the Team first needs to authorize it.

[rohitg00]

Hey @Tanmay-008 , Thanks for the issues, We wil discuss this internally today.