improve: ObjectPool to Dynamic Allocation and update condition creation

[dudantas]

Description

This commit refactors the ObjectPool implementation to support dynamic allocation without requiring a fixed capacity. It updates the Condition::createCondition method to use the new dynamic pool for all condition types. The refactor improves memory reuse and provides a more flexible design for future scalability.

Behaviour

Actual

The ObjectPool required a fixed capacity (1024), limiting its flexibility and causing issues with scaling.

Expected

The ObjectPool now dynamically allocates objects as needed, eliminating the need for a fixed capacity.

Type of change

• New feature (non-breaking change which adds functionality)

How Has This Been Tested

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.

• Manual testing with multiple condition types to verify proper allocation and deallocation.
• Reviewed performance under high load to ensure dynamic pooling works as expected.

Test Configuration:

• Server Version: Canary MMORPG Emulator (Latest)
• Client: Not specified
• Operating System: Windows/Linux

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I checked the PR checks reports
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud