fix(workflow): use correct field ID in KB metadata filter selection

[shawny011717]

Important

1. Make sure you have read our contribution guidelines
2. Ensure there is an associated issue and you have been assigned to it
3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

Fixes #33577.
fix #35844

The onClick handler in the metadata field dropdown (AddCondition component) was attached to the inner text <div> instead of the outer row <div>. This meant clicks landing on the icon, type label, or row padding did not register the intended field — the resulting mis-hit caused the UI to appear to always select the first field. Moving the handler to the row element ensures the full clickable area maps to the correct metadata item.

Screenshots

N/A (logic-only fix, no visual change)

Checklist

• This change requires a documentation update, included: Dify Document
• I understand that this PR may be closed in case there was no previous discussion or issues. Contribution guidelines
• I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
• I've updated the documentation accordingly.
• I ran cd web && npx lint-staged to appease the lint gods

[shawny011717]

Gentle ping — this one's been waiting ~3 weeks for review. Happy to rebase or break it into smaller diffs if that helps. 🙏

[hjlarry]

the origin fix only handles clicks on the full row, not only the field name text

the reason is Built-in fields all share the same metadata_id value (built-in), so matching by metadata_id alone could incorrectly display every built-in condition as document_name.

also fix a layering issue where the dropdown could be hidden behind the metadata panel.