fix(sqlite3): fix version name, remove "+"

[HOMODELUNA]

• Before adding new features and new modules, please go to issues to submit the relevant feature description first.
• Write good commit messages and use the same coding conventions as the rest of the project.
• Please commit code to dev branch and we will merge into master branch in feature
• Ensure your edited codes with four spaces instead of TAB.

---

• 增加新特性和新模块之前，请先到issues提交相关特性说明，经过讨论评估确认后，再进行相应的代码提交，避免做无用工作。
• 编写友好可读的提交信息，并使用与工程代码相同的代码规范，代码请用4个空格字符代替tab缩进。
• 请提交代码到dev分支，如果通过，我们会在特定时间合并到master分支上。
• 为了规范化提交日志的格式，commit消息，不要用中文，请用英文描述。

见 issue #8490

[gemini-code-assist]

Summary of Changes

Hello @HOMODELUNA, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an inconsistency in how SQLite3 package versions are handled within the xmake build system. It standardizes the version naming by removing custom build suffixes from version strings and refining the logic used to generate download URLs, ensuring that package retrieval and registration adhere to a more conventional semantic versioning format.

Highlights

• Version String Generation Logic: The method for constructing the version_str used in the SQLite download URL has been refactored. Instead of using gsub to remove . and + characters and then padding, it now explicitly formats the major, minor, and patch components of the version.
• Standardized Version Naming: All add_versions entries for SQLite3 have been updated to remove the non-standard + suffix and its associated build number (e.g., "3.23.0+0" becomes "3.23.0", "3.34.0+100" becomes "3.34.1"). This ensures a cleaner and more consistent versioning scheme.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly addresses an issue with non-standard version strings for the sqlite3 package, which was causing problems with version resolution. By normalizing the version strings to be compliant with semantic versioning and updating the URL generation logic accordingly, the changes significantly improve the correctness and maintainability of the package definition. The new logic for generating the version string for the download URL is much clearer and more robust than the previous implementation. I have one minor suggestion regarding code formatting to further improve readability.