feat: make kind chip clickable to filter logs by kind

[crackedhandle]

Fixes #9558

Problem

Users reported (via the 2025 DevTools user survey) that clicking on tags
in the log event rows had no effect. There was no way to quickly filter
logs by a specific kind (e.g. stderr, flutter.error) by clicking on
the kind chip directly.

Solution

Made the kind chip in the log event rows clickable. When a user clicks
on a kind chip, it automatically applies a k:<kind> filter to the logs
table, showing only logs of that kind.

Changes

• Added an optional onKindTapped callback parameter to MetadataChips
  widget in metadata.dart
• Added an optional onTap callback to the base MetadataChip class
• Wrapped the chip with GestureDetector and MouseRegion when onTap
  is provided, showing a pointer cursor on hover to indicate it is clickable
• In _message_column.dart, passed an onKindTapped callback to
  MetadataChips that calls controller.setActiveFilter(query: 'k:$kind')
  when the kind chip is tapped

Behavior

• Clicking a kind chip → applies a k:<kind> filter to the logs table
• Clicking the row outside the tag → still selects the log as before
• No breaking changes → onKindTapped is optional, so existing
  usages of MetadataChips without the callback are unaffected

Testing

Manually tested by:

1. Running a Flutter app connected to DevTools
2. Opening the Logging screen
3. Clicking on a kind chip (e.g. flutter.frame) in a log row
4. Verified that the filter field updates to k:flutter.frame and only
   logs of that kind are shown
5. Verified that clicking outside the chip still selects the log row

[gemini-code-assist]

Code Review

This pull request enables filtering of logs by their kind when tapping on the metadata chips in the logging screen. It introduces an onKindTapped callback to the MetadataChips and MetadataChip widgets, allowing the LoggingController to update the active filter. Feedback was provided to improve the robustness of the filter query by wrapping the kind in quotes to handle spaces and to refine the interactive area of the chips by moving the margin outside of the gesture detector.

[crackedhandle]

@kenzieschmoll can you please take a look, and suggest me if any corresponding changes needed.

[kenzieschmoll]

Can you please include a .gif showing the new behavior?

[kenzieschmoll]

define the callback here directly instead of passing it in from the MetadataChips constructor. As is, there is an unnecessary level of abstraction to pass it in from MetadataChips.

[kenzieschmoll]

can we use an Inkwell instead of MouseRegion + GestureDetector?

[kenzieschmoll]

furthermore, it should be possible to use an Inkwell with a null onTap handler that will behave as if the Inkwell were not present in the tree. This should make it possible to revert the changes above to store chip as a local variable and just define everything in the return statement.

[kenzieschmoll]

please address comments and add tests. thanks.

[kenzieschmoll]

Please also add logic to apply filters for all the chips, not just the kind chips (e.g. log level, zone, isolate, etc.)