controller test

[s2oBCN]

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

As said in this request #9468 this is an example of IT.
I had to improve the Factory Pattern of the APP splitting the code in 2 classes one the factory and the other the app entry point (as described here here https://medium.com/@ferrohardian/application-factory-pattern-starting-your-flask-project-e17dd2f12013). Without this improviment the test executes two times the create_app method.

Fixes #9468

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

• End to end test: execute the hole system to verify that the split of the app.py doesn't break anything
• Integration test: execute the integration test created with debug from vscode and see that the app stops in the breaking point in the controller and returns 200.