feat:add apollo configuration to load env file

[huanshare]

Summary

Please note:dify supports loading env file configuration from the configuration-center(apollo). If you use apollo, first configure the dify configuration on apollo, and then before starting the project, configure the following parameters in the environment variables:
CONFIGURATION_TYPE=apollo,APOLLO_APP_ID=xxx,APOLLO_CLUSTER=xxx,APOLLO_CONFIG_URL=xxx,APOLLO_NAMESPACE=xxx

Close #11064

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]

Could you avoid overwriting the local file? I think it's better to update dify_config object directly.

[huanshare]

Is there such a situation: if the env file and the configuration center have the same key but different value configurations, the configuration in the configuration center and the configuration in the server env file will be inconsistent, which may cause trouble for other developers