[fit] optimize test framework to support executing specific actions at test startup

[CodeCasterX]

🔗 相关问题 / Related Issue

Issue 链接 / Issue Link: Closes #204

• 我已经创建了相关 Issue 并进行了讨论 / I have created and discussed the related issue
• 这是一个微小的修改（如错别字），不需要 Issue / This is a trivial change (like typo fix) that doesn't need an issue

📋 变更类型 / Type of Change

• 🐛 Bug 修复 / 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)
• 📚 文档更新 / Documentation update
• 🔧 重构 / Refactoring (no functional changes)
• ⚡ 性能优化 / Performance improvement
• 🧹 代码清理 / Code cleanup

📝 变更目的 / Purpose of the Change

This change optimizes the test framework to support database access operations within Bean constructors. Previously, the framework couldn't properly handle scenarios where business logic Beans perform database operations during initialization, leading to test failures or inconsistent behavior. This enhancement adds specific execution phases to ensure proper database connection management and transaction handling during Bean construction in test environments.

📋 主要变更 / Brief Changelog

• Added new execution phase for Bean constructor database access support
• Implemented database connection initialization before Bean construction phase
• Enhanced transaction management for constructor-level database operations
• Added configuration options for controlling database access timing during tests
• Improved test lifecycle management to handle database-dependent Bean initialization

🧪 验证变更 / Verifying this Change

测试步骤 / Test Steps

1. Create a test Bean with database access operations in its constructor
2. Configure the test framework to use the new execution phase
3. Run tests to verify that database connections are properly established before Bean construction
4. Verify that transactions are correctly managed during Bean initialization
5. Confirm that existing tests continue to pass without modification

测试覆盖 / Test Coverage

• 我已经添加了单元测试 / I have added unit tests
• 所有现有测试都通过 / All existing tests pass
• 我已经进行了手动测试 / I have performed manual testing

📸 截图 / Screenshots

✅ 贡献者检查清单 / Contributor Checklist

请确保你的 Pull Request 符合以下要求 / Please ensure your Pull Request meets the following requirements:

基本要求 / Basic Requirements:

• 确保有 GitHub Issue 对应这个变更（微小变更如错别字除外）/ Make sure there is a Github issue filed for the change (trivial changes like typos excluded)
• 你的 Pull Request 只解决一个 Issue，没有包含其他不相关的变更 / Your PR addresses just this issue, without pulling in other changes - one PR resolves one issue
• PR 中的每个 commit 都有有意义的主题行和描述 / Each commit in the PR has a meaningful subject line and body

代码质量 / Code Quality:

• 我的代码遵循项目的代码规范 / My code follows the project's coding standards
• 我已经进行了自我代码审查 / I have performed a self-review of my code
• 我已经为复杂的代码添加了必要的注释 / I have commented my code, particularly in hard-to-understand areas

测试要求 / Testing Requirements:

• 我已经编写了必要的单元测试来验证逻辑正确性 / I have written necessary unit-tests to verify the logic correction
• 当存在跨模块依赖时，我尽量使用了 mock / I have used mocks when cross-module dependencies exist
• 基础检查通过：mvn -B clean package -Dmaven.test.skip=true，elsa README 中的编译检查 / Basic checks pass
• 单元测试通过：mvn clean install / Unit tests pass

文档和兼容性 / Documentation and Compatibility:

• 我已经更新了相应的文档 / I have made corresponding changes to the documentation
• 如果有破坏性变更，我已经在 PR 描述中详细说明 / If there are breaking changes, I have documented them in detail
• 我已经考虑了向后兼容性 / I have considered backward compatibility

📋 附加信息 / Additional Notes

Breaking Change Notice:
This PR introduces a breaking change to the @SQL annotation in the test framework. The original scripts attribute has been removed and replaced with before and after attributes. The previous scripts attribute only represented pre-execution scripts and didn't consider post-execution scenarios. The new design provides:

• before attribute: Scripts executed before the test
• after attribute: Scripts executed after the test

This change requires updating existing test code that uses the @SQL annotation's scripts attribute to use the new before attribute instead.

Migration Guide:

// Old usage (deprecated)
@Sql(scripts = "classpath:test-data.sql")

// New usage
@Sql(before = "classpath:test-data.sql")

Other Enhancements:
This enhancement optimizes Bean constructor database access support through new execution phases. The new execution phase is only activated when Beans with constructor database access are detected. Performance impact is minimal as the optimization only applies to relevant scenarios.

Future improvements may include:

• Support for more complex database initialization patterns
• Enhanced error handling for database connection failures during Bean construction
• Additional configuration options for fine-tuning execution phases

---

审查者注意事项 / Reviewer Notes:

Please pay special attention to:

• The new execution phase implementation and its integration with existing test lifecycle
• Database connection management logic in Bean constructor scenarios
• Transaction handling during Bean initialization
• Backward compatibility with existing test configurations
• Performance implications of the new execution phase