[FR] Extend rules database layout: support i18n and version detection about libchecker

[qhy040404]

Internationalizing the description is a good idea, but at present, the database is manually maintained and is not integrated into ci. This will be a lot of work.
Secondly, it is not realistic to maintain the version information. Not all libraries will be published in maven central, and some libraries will be released separately through aar or jar. These content published on the open platform may not be available to the public, and applying for relevant permissions is also part of the overhead.
If the database is revised in the future, I will prefer to design a back-end, because at present, a large number of jsons correspond to the same description.
At present, LibChecker does not involve profit, and it is not necessarily in the future. It may be unrealistic to maintain a back-end. The current solution may be relatively cost-effective.