Fix duplicate SQLite entry and add APEX Launcher

[reza-ygb]

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

Summary by Sourcery

Update README to remove a duplicate SQLite entry and add APEX Launcher to the list of Linux launchers

Documentation:

• Remove the duplicated SQLite entry in the database tools section of the README
• Add APEX Launcher entry under the Linux application launcher listings in the README

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR cleans up a duplicate SQLite entry and augments the application launcher section by adding APEX Launcher, all within the README.

Entity relationship diagram for database section in the README after duplicate SQLite removal

erDiagram
    SQLITE {
      string name
      string description
      string link
    }
    SQLITE_BROWSER {
      string name
      string description
      string link
    }
    WEBDB {
      string name
      string description
      string link
    }
    SQLITE ||--|| SQLITE_BROWSER : "can open"
    SQLITE ||--|| WEBDB : "can connect"

Loading

File-Level Changes

Change	Details	Files
Remove redundant SQLite listing	Eliminated the duplicate SQLite entry in the database section Adjusted surrounding list formatting to maintain consistency	README.md
Add APEX Launcher to application launchers list	Inserted APEX Launcher entry with link and brief description Ensured list style matches existing launcher entries	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[reza-ygb]

Hi, I've added APEX Launcher to the list and also removed a duplicate entry I noticed.
Let me know if any changes are needed. Thanks for maintaining this great project!