fix: resolve database connection leak issue in ORM extension

[jairajc]

We highly recommend you read the contributor's documentation before starting the review process especially since this is your first contribution to this project.

It was updated on 2024/5/27

What type of PR is this?

fix: database connection leak in ORM extension

What this PR does / why we need it:

This PR addresses a critical database connection leak issue in the atest-ext-store-orm extension that causes "too many connections" errors when switching between different database configurations in production environments.

Key Changes:

• Fixed context leak in cmd/run.go by properly handling context cancellation with defer
• Ready-to-apply patch file for the atest-ext-store-orm extension with connection pool improvements
• Complete test suite validating connection lifecycle management and leak prevention
• Composite cache key implementation (store:database) to prevent connection reuse conflicts

Technical Details:
The root cause was identified in the ORM extension's getClientWithDatabase method where cache keys only used database names, causing connection conflicts when switching between different store configurations pointing to the same database. The fix implements proper connection pooling, thread-safe caching, and composite cache keys.

Impact:

• Resolves issues with database connection exhaustion
• Prevents "too many connections" MySQL errors during database switching
• Improves system stability and resource management
• Provides comprehensive testing framework for connection management

Which issue(s) this PR fixes:

Addresses database connection leak issues reported in production environments when using multiple database configurations with the ORM extension.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ jairajc
❌ Jai Raj Choudhary

---

Jai Raj Choudhary seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[LinuxSuRen]

Thanks for your time. But there are a few small issues you might need to handle.

[LinuxSuRen]

hi @jairajc , thanks for your effort. Everything is ok except the following you need to handle before merging this PR.

• Please use your email that connects to your GitHub account
• Please feel free to complete the CLA according to the instructions

[sonarqubecloud]

Quality Gate passed

Issues
0 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