Add comprehensive tests for routing and performance monitoring

[CAFernandes]

• Implemented PerformanceMonitorTest to validate performance metrics tracking, including request lifecycle, memory monitoring, error rate tracking, and performance thresholds.
• Created ArrayCallableTest to ensure array callable routing functionality, including instance and static methods, parameter extraction, and middleware support.
• Developed ParameterRoutingTest to cover various parameter routing scenarios, including constraints, optional parameters, and nested groups.
• Added TestController to support routing tests with sample methods for handling requests.

Pull Request Template

📋 Descrição

Descreva resumidamente as mudanças feitas neste PR.

🎯 Tipo de Mudança

• 🐛 Bug fix (mudança que corrige um bug)
• ✨ Nova feature (mudança que adiciona funcionalidade)
• 💥 Breaking change (mudança que causa incompatibilidade)
• 📚 Documentação (mudanças apenas na documentação)
• 🧹 Refactoring (mudanças que não corrigem bug nem adicionam feature)
• ⚡ Performance (mudanças que melhoram a performance)
• 🧪 Testes (adição ou correção de testes)

🧪 Como foi testado?

Descreva os testes que você executou para verificar suas mudanças.

• Testes unitários passando
• Testes funcionais passando
• Testado manualmente
• Exemplos funcionando

📝 Checklist

• Meu código segue as diretrizes de estilo do projeto
• Eu fiz uma auto-revisão do meu código
• Comentei meu código, especialmente em partes difíceis de entender
• Fiz mudanças correspondentes na documentação
• Minhas mudanças não geram novos warnings
• Adicionei testes que provam que minha correção é eficaz ou que minha feature funciona
• Testes unitários novos e existentes passam localmente com minhas mudanças

[Copilot]

Pull Request Overview

This PR adds a broad suite of unit, stress, and integration tests to verify routing behavior and performance monitoring features in PivotPHP.

• Introduced TestController and related unit tests for array callable routing and parameterized routes.
• Added PerformanceMonitorTest and HighPerformanceModeTest to cover performance metrics and high-performance mode behavior.
• Updated stress tests to use DynamicPoolManager and removed runtime logging in favor of CI/CD assertions.

Reviewed Changes

Copilot reviewed 57 out of 57 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
tests/Unit/Routing/TestController.php	Added controller class to support routing tests.
tests/Unit/Routing/ParameterRoutingTest.php	Comprehensive parameter-based routing scenarios.
tests/Unit/Routing/ArrayCallableTest.php	Tests for instance/static array callables and middleware support.
tests/Stress/HighPerformanceStressTest.php	Switched to DynamicPoolManager and replaced logs with assertions.
tests/Performance/PerformanceMonitorTest.php	Unit tests for PerformanceMonitor lifecycle and metric tracking.
tests/Performance/HighPerformanceModeTest.php	Unit tests for enabling/disabling high-performance mode and monitor.
tests/Integration/Routing/ArrayCallableIntegrationTest.php	Full-application integration tests for array callables.
tests/Integration/Routing/ArrayCallableExampleTest.php	Example integration tests demonstrating array callable usage.

Comments suppressed due to low confidence (2)

tests/Unit/Routing/ParameterRoutingTest.php:153

• The test for optional parameters does not include any assertion for $route2; consider adding an assertion (e.g., assertNotNull or assertNull depending on expected behavior) to validate handling of missing optional parameter.

        $route2 = Router::identify('GET', '/search/php');

tests/Unit/Routing/ArrayCallableTest.php:197

• [nitpick] Hardcoding the exact exception message may make the test brittle; consider matching only the exception class or using assertStringContainsString to allow minor message changes without breaking the test.

        $this->expectExceptionMessage('Handler must be a callable function');