fix(lark_trigger): fix serialization error for bitable record changed

[Night-stars-1]

Related Issues or Context

Fixed a PydanticSerializationError triggered when processing Bitable record change events.
The before_value and after_value fields contain instances of BitableTableRecordActionField. Since this class does not inherit from Pydantic's BaseModel, it causes a serialization failure when the event data is handled by Pydantic-based components

Solution:
Manually transform the BitableTableRecordActionField objects into standard dictionaries by extracting field_id and field_value. This ensures the action_info object consists only of JSON-serializable Python primitives.

This PR contains Changes to Non-Plugin

• Documentation
• Other

This PR contains Changes to Non-LLM Models Plugin

• I have Run Comprehensive Tests Relevant to My Changes

Before:

After:

This PR contains Changes to LLM Models Plugin

• My Changes Affect Message Flow Handling (System Messages and User→Assistant Turn-Taking)

• My Changes Affect Tool Interaction Flow (Multi-Round Usage and Output Handling, for both Agent App and Agent Node)

• My Changes Affect Multimodal Input Handling (Images, PDFs, Audio, Video, etc.)

• My Changes Affect Multimodal Output Generation (Images, Audio, Video, etc.)

• My Changes Affect Structured Output Format (JSON, XML, etc.)

• My Changes Affect Token Consumption Metrics

• My Changes Affect Other LLM Functionalities (Reasoning Process, Grounding, Prompt Caching, etc.)

• Other Changes (Add New Models, Fix Model Parameters etc.)

Version Control (Any Changes to the Plugin Will Require Bumping the Version)

• I have Bumped Up the Version in Manifest.yaml (Top-Level Version Field, Not in Meta Section)
  0.0.3 → 0.0.4

Dify Plugin SDK Version

• I have Ensured dify_plugin>=0.3.0,<0.6.0 is in requirements.txt (SDK docs)
  Note: The current requirements.txt specifies dify_plugin>=0.5.0 which was already the case before this PR.

Environment Verification (If Any Code Changes)

Local Deployment Environment

• Dify Version is: 1.13.1, I have Tested My Changes on Local Deployment Dify with a Clean Environment That Matches the Production Configuration.

SaaS Environment

• I have Tested My Changes on cloud.dify.ai with a Clean Environment That Matches the Production Configuration

[gemini-code-assist]

Code Review

This pull request updates the Lark Bitable record change event to process before_value and after_value as structured lists of field IDs and values, and increments the manifest version. Feedback highlights a typo in the after_value logic and a schema inconsistency where the YAML definition uses object instead of array for the new list-based fields.

[gemini-code-assist]

There is a typo in the conditional check for field_value. It currently checks after_value_item.field_id instead of after_value_item.field_value. This makes the logic inconsistent with the before_value processing on line 54 and may result in None being assigned to field_value if the actual value is None but the field_id exists.

Suggested change

	"field_value": after_value_item.field_value if after_value_item.field_id else ""
	"field_value": after_value_item.field_value if after_value_item.field_value else ""