fix: apply gevent threading patch early and ensure unique workflow node execution IDs

[laipz8200]

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.

1. Use a new UUID as the primary key of the workflow node execution record.
2. Remove the version warning message.
3. Make sure to apply patching before importing the app.
4. Remove the threading utils file because Gevent does not only patch the threading module.

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

[bowenliang123]

Forcibly applying gevent theading patch in all cases may cause the following consequences:

1. failed to debug on local enviroment
2. failed to start the worker service, when the gevent is not used as the execution pool workder class, eg. threads or processes.

Consider to ignore or check these situations please.

[laipz8200]

Forcibly applying gevent theading patch in all cases may cause the following consequences:

1. failed to debug on local enviroment

2. failed to start the worker service, when the gevent is not used as the execution pool workder class, eg. threads or processes.

Consider to ignore or check these situations please.

Thanks for the suggestions, but I found we can only use the Gevent worker for now.

[bowenliang123]

Alright. It's just a minor reminder for you, not a blocker issue anyway.
CELERY_WORKER_CLASS in api/entrypoint.sh of the api docker image is allowing usage of implementation classes other than gevent.