refactor: simplify some exception catch code

[acelyc111]

Summary

In #11955, some exceptions are changed to derive from ValueError, so the related exception catch code can be simplifed.

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]

We've changed those exceptions to ValueError in #11955.

[acelyc111]

We've changed those exceptions to ValueError in #11955.

So all code like except (ValueError, AppInvokeQuotaExceededError) as e: can be simplified to except ValueError as e:, right?

[laipz8200]

We've changed those exceptions to ValueError in #11955.

So all code like except (ValueError, AppInvokeQuotaExceededError) as e: can be simplified to except ValueError as e:, right?

Yes.

[laipz8200]

LGTM