perf(api): optimize token read/write during api call

[aconeshana]

Checklist:

Important

Please review the checklist below before submitting your pull request.

• Please open an issue before creating a PR or link to an existing issue
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

Description

1. Since Dify uses Redis, token authentication can be optimized by storing it in Redis.
2. Each time a token is used, the last updated timestamp will be refreshed asynchronously via Celery.

Closes #9950

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update, included: Dify Document
• Improvement, including but not limited to code refactoring, performance optimization, and UI/UX improvement
• Dependency upgrade

Testing Instructions

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[aconeshana]

related issue: #9950

[crazywoola]

LGTM

[aconeshana]

The following is the benchmark report

env(production):
helm on k8s 4C 32G 4 dify-api instance

benchmark conf

1. 400 concurrent thread

2. 2000loop
   

3. workflow sse api without llm(Excluding the impact of LLM), input&output
   

baseline:

new head:

Summary:

1. Significant reduction in anomaly spike
2. error rate from 0.11% to 0.08%, mainly due to 502 errors caused by Kubernetes CPU limit
3. RT reduce

[crazywoola]

Please resolve the conflict files.