Replace BeanPostProcessor with explicit proxy for DataSource instrumentation

[rajeswari2904]

FIxes Issue #13512

• Refactored DataSource instrumentation from BeanPostProcessor to explicit proxy wrapping.
• Added ProxyFactory to wrap the DataSource to prevent double wrapping and scoped proxy issues.
• Ensured compatibility with Spring AOP by invoking methods via reflection on the proxy.
• Maintained configuration-driven settings for statement sanitization, query parameter capture, and transaction instrumentation.
• Improved handling for multiple DataSources and scoped proxies.
• Preserved original bean order with minimal impact on other bean post-processors.
• This change resolves issues related to double instrumentation and method interception failures.
• Simplified debugging and enhanced maintainability by making DataSource wrapping explicit.

[linux-foundation-easycla]

• ✅ login: otelbot[bot] (2147d93)
• ✅ login: laurit / name: Lauri Tulmin (a5609e6)
• ❌ - login: @rajeswari2904 / name: Rajeswari . The commit (a24bd0a) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[otelbot-java-instrumentation]

🔧 The result from spotlessApply was committed to the PR branch.

[laurit]

Firstly the title of the PR is misleading. BeanPostProcessor is still there and not replaced with anything. Secondly a test should be added. Thirdly there should be a comment in the code explaining why such proxying is used.