feat: support concurrently handle local plugins launching

[bowenliang123]

• Currently, all the local plugins are being checked and initialising the Python environment sequentially. And the pre-compiling each single Python file one by one in the plugin and its dependency in the InitPythonEnvironment method slows the uptime for plugin launching
• This PR brings concurrency in handling local plugins, which speeds up the plugin launching time dramatically, especially for a new empty plugin-daemon instance.

[Yeuoly]

Actually, concurrently launching was supported already, PluginManager.maxLaunchingLock is what you want, it already limited concurrency of how many plugins could launch at the same time inside launchLocal, just feel free to launch them at the same time, and wait for all of them to finished.

[bowenliang123]

Actually, concurrently launching was supported already, PluginManager.maxLaunchingLock is what you want, it already limited concurrency of how many plugins could launch at the same time inside launchLocal, just feel free to launch them at the same time, and wait for all of them to finished.

Curious to hear that concurrency has been supported in launching local plugins, while in practise we don't see evidence in concurrently installed and launching local plugins.

And BTW, config.PluginLocalLaunchingConcurrent config is existed but never used across the project without this PR.

[Yeuoly]

It's no need to use semaphores as pluginManager will automatically control its limits