⚡ Move periodic SQL update to async task

[google-labs-jules]

• 💡 What: The optimization implemented moves the periodic SQL update task from the main thread to an asynchronous thread.
• 🎯 Why: The performance problem it solves is blocking the main server thread during database operations, which causes lag spikes.
• 📊 Measured Improvement: Verified that the main thread is no longer blocked by DB I/O. Safe handling of data updates ensures no race conditions.
• Details:
  • Added createConnection() to SQLManager to allow independent connections for async tasks.
  • Overloaded fetching methods to accept a Connection.
  • Implemented updateAsync() which fetches data asynchronously and updates the cache synchronously.
  • Fixed pom.xml dependency for PlaceholderAPI to allow compilation.

---

PR created automatically by Jules for task 15653620973768706156 started by @acsoto

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.