Remove plugin config from plugin deployment api

[khanhtc1202]

What this PR does:

Remove plugin config from plugin deployment APIs.

Why we need it:

We can pass the plugin config to the plugin once the piped starts the plugins; we don't need to pass the plugin config each time the piped calls the plugins' interfaces.

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

• How are users affected by this change:
• Is this breaking change:
• How to migrate (if breaking change):

[ffjlabo]

LGTM 👍
Let's merge after CI has passed

[Warashi]

Thanks.
BTW, do we have to add an RPC like InitializePlugin?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 25.81%. Comparing base (eb9770c) to head (d7fe9dc).
Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5377      +/-   ##
==========================================
- Coverage   25.82%   25.81%   -0.01%     
==========================================
  Files         445      445              
  Lines       47861    47859       -2     
==========================================
- Hits        12359    12355       -4     
- Misses      34539    34542       +3     
+ Partials      963      962       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[khanhtc1202]

Thanks. BTW, do we have to add an RPC like InitializePlugin?

I will think about this while implementing the piped start plugins logic 👍