fix: better type to MutableMapping

[yihong0618]

Summary

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Tip

Close issue syntax: Fixes #<issue number> or Resolves #<issue number>, see documentation for more details.

Screenshots

Before	After
...	...

Checklist

Important

Please review the checklist below before submitting your pull request.

• 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. (This doesn't apply to typos!)
• 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 dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

[laipz8200]

Thank you for the contribution!

Although MutableMapping can offer more flexible type annotations compared to dict, I believe this doesn't quite align with our expectations: we want all dictionaries passed as parameters to be immutable.

[yihong0618]

so keep the old way dict（input) is ok? If so I will close it

[laipz8200]

It's okay to change dict to MutableMapping, but I think we should avoid changing Mapping to MutableMapping.

[yihong0618]

It's okay to change dict to MutableMapping, but I think we should avoid changing Mapping to MutableMapping.

copy that will change it

[laipz8200]

I'm sorry I didn't explain my intention clearly. In this method, we indicate to the caller that the inputs won't be directly modified by marking the parameters as a Mapping type. Then, on line 34, we make a copy of the inputs, and finally, we provide the modified inputs as a return value for the user.

[yihong0618]

sorry for forget it will change these days.