feat(plugin): Add Key-Value Storage Support for Plugins

[sosyz]

This pull request introduces a new key-value storage system for plugins. The most important changes include adding a new entity for plugin key-value storage, creating a migration for the new table, updating the plugin service to use the new storage, and implementing the key-value storage functionality.

Key-Value Storage System for Plugins

• internal/entity/plugin_kv_storage_entity.go: Added a new PluginKVStorage entity to represent the key-value storage for plugins.

• internal/migrations/init_data.go: Included the PluginKVStorage entity in the initial data setup.

• internal/migrations/migrations.go: Added a new migration to create the plugin_kv_storage table.

• internal/migrations/v25.go: Implemented the addPluginKVStorage function to handle the migration for the new table.

• internal/service/plugin_common/plugin_common_service.go: Updated the PluginCommonService to initialize the key-value storage database connection.

Implementation of Key-Value Storage Functionality

• plugin/kv_storage.go: Implemented the KVOperator struct and methods for handling key-value storage operations, including setting, getting, and deleting values, as well as transaction management.

• plugin/plugin.go: Updated the plugin registration to handle key-value storage plugins and defined the Data struct to avoid circular dependencies. [1] [2]

Testing

I've created a test plugin to validate this functionality

Would it be helpful to include test code files in the repository? Have any suggestions on how to better demonstrate and test this feature.

This enhancement provides plugins with persistent storage capabilities, enabling more complex plugin functionality and state management.

Related Issue

Closes #1208

Looking forward to feedback!

[LinkinStars]

Wrap these query conditions in an object so that subsequent extensions do not affect the previous developer. I think it's possible to add a query later.

[LinkinStars]

I've created a test plugin to validate this functionality

Would it be helpful to include test code files in the repository? Have any suggestions on how to better demonstrate and test this feature.

@sosyz I think you wrote a great test case and like you said, it should be added to this repository(maybeplugin_test dir). To facilitate subsequent testing. I've tested the others, and the function itself should be fine. Great.

[sosyz]

Some update: I've added high concurrency tests and discovered issues that I'm currently working to resolve.