[DSIP-44] Add owner for provider managed plugins

### Search before asking

- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.

### Description

IMHO we could classify current plugins into two categories:

1. Community-Managed plugins: widely-used plugins such as shell, hive, spark, flink, etc.
2. Provider-Managed plugins: plugins used in specific scenario, which enriches the open-source ecosystem of Dolphin.

With the growing number of provider-managed plugins, the community do not have enough hands to ensure the stability and security. Therefore, I suggest each provider-managed plugin should have an owner, responsible for the stability and security issues. Before each release of Dolphin, we need the owners to submit a test report for the plugins they cover. Failure to submit test reports within release date for three consecutive times will lead to the retirement of the plugin.

We could call for a vote later to decide which plugins will be managed by the community.

[WIP] Community-Managed Plugins:
* shell
* hive
* spark
* flink
* ......

[WIP] Provider-Managed Plugins:
|Name|Owner|
| -------- | ------- |
|dataquality-plugin||
|zeppelin-plugin|@EricGao888|
|jupyter-plugin|@EricGao888|
......

### Are you willing to submit a PR?

- [ ] Yes I am willing to submit a PR!

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)