[FeatureRequest] Make the users that use your published workflow/tool use their own API KEY

[Emasoft]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I discovered with horror that published workflows/tools can be used by other users (nothing strange here) but that also the workflow will use my API KEY instead of that of the user (and this is very strange!). This is clearly wrong, and should be solved ASAP making Dify to ask the user to add the API KEY needed by the app/tool to their Dify configuration, and automatically use that one. Never an user should be able to explot the API KEY of the developer when he publish a web app/tool on Dify cloud.

2. Additional context or comments

No response

3. Can you help us with this feature?

• I am interested in contributing to this feature.