fix: refactor all 'or []' and 'or {}' logic to make code more clear

[yihong0618]

Summary

refactor most of the or [] and or {} logic
main is as it

• since we use dict.get(xxx) can use default value
• some value is already [] by default there is no need to or it

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]

This behavior is unexpected because sometimes the dictionary contains entries with {'key': None}.

[laipz8200]

However, some parts of the changes are worth keeping, and we can retain those. Could you avoid changing the dict.get('key') pattern while keeping the other modifications?

[yihong0618]

This behavior is unexpected because sometimes the dictionary contains entries with {'key': None}.

yes I did not change that logic, please check~

[yihong0618]

copy that, will change the dict key, None part I am wrong

[yihong0618]

However, some parts of the changes are worth keeping, and we can retain those. Could you avoid changing the dict.get('key') pattern while keeping the other modifications?

fixed thanks

[laipz8200]

Two points might need changed, please check my comments. 😊

[laipz8200]

Thank you for your detailed work~

[bowenliang123]

LGTM. Nice shots~