feat: add compose project name for docker compose

[XenoAmess]

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.

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

[crazywoola]

Hello please open an issue first. :)

[kurokobo]

Related to: #8327 (comment)

Sorry, we can not accept this PR, because this changes may affect existing users who already start with the old compose configuration.

We decide to leave it as an optional with docker compose up -d -p dify.

So if we accept this PR, I think the default value should be docker to avoid affecting existing environment.

[XenoAmess]

Related to: #8327 (comment)

Sorry, we can not accept this PR, because this changes may affect existing users who already start with the old compose configuration.
We decide to leave it as an optional with docker compose up -d -p dify.

So if we accept this PR, I think the default value should be docker to avoid affecting existing environment.

but logically you ARE dify, but NOT docker...
considering other guys doing such things too, that would be a disaster.
please consider this when enter next major update(when need not consider too many backward compa.)