Add HTTP Server capabilities and provide external HTTP API

[zwmagic]

What would you like to be added?

Add support for HTTP server to the Sermant framework and provide its own HTTP API endpoint

Why is this needed?

HTTP API capabilities enhance Sermant's functionality and interoperability. For example, it can implement health check, monitoring indicator collection, service registration and discovery, dynamic installation and uninstallation of plug-ins, plug-in customization functions, etc.

plan

After introducing the HTTP server capability, Sermant's core functions and each plug-in can independently provide their own HTTP API services.

All externally exposed APIs will follow the following format: http://localhost:{port}/{pluginName}/{specificPath}. In this structure:

• localhost refers to the host address where the Sermant service runs.
• {port} is the port number that the Sermant service listens on, allowing users to customize it.
• {pluginName} refers to the name of the plugin requesting the service. When the requested service belongs to Sermant core functionality, the value of pluginName will be set to "sermant".
• {specificPath} is the specific API path provided by the plugin.

[github-actions]

This issue seems to be Stale. We will close it in a few days.