Add DeployTargetsByPlugin to Web API

[khanhtc1202]

What this PR does:

as title

Why we need it:

These API will be used by forms in Web UI to register and edit application

Which issue(s) this PR fixes:

Part of #5252

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):

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 19 lines in your changes missing coverage. Please review.

Project coverage is 26.42%. Comparing base (ed28c89) to head (0b0e63c).
Report is 6 commits behind head on master.

Files with missing lines	Patch %	Lines
pkg/app/server/grpcapi/web_api.go	0.00%	12 Missing ⚠️
pkg/datastore/datastoretest/datastore.mock.go	0.00%	4 Missing ⚠️
pkg/datastore/applicationstore.go	0.00%	2 Missing ⚠️
pkg/app/server/grpcapi/api.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5556      +/-   ##
==========================================
- Coverage   26.43%   26.42%   -0.01%     
==========================================
  Files         465      465              
  Lines       49901    49913      +12     
==========================================
  Hits        13189    13189              
- Misses      35657    35669      +12     
  Partials     1055     1055              

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

[ffjlabo]

Maybe add req.DeployTargetsByPlugin as args?

Suggested change

	if err := a.applicationStore.UpdateConfiguration(ctx, req.ApplicationId, req.PipedId, req.PlatformProvider, req.GitPath.ConfigFilename, nil); err != nil {
	if err := a.applicationStore.UpdateConfiguration(ctx, req.ApplicationId, req.PipedId, req.PlatformProvider, req.GitPath.ConfigFilename, req.DeployTargetsByPlugin); err != nil {

[khanhtc1202]

I don't update api service.proto (API for pipectl and external tool), so there is no req.DeployTargetsByPlugin, just pass nil here and not update the grpc for this API since this one is used by pipectl and outer tool (like https://github.com/pipe-cd/terraform-provider-pipecd), I will consider to update this later

[ffjlabo]

@khanhtc1202 I got it and OK to consider later. So it would be nice to add a comment about the context.

IMO, we need to update the API for pipectl and external tool because it will update as nil when adding the app and later update via pipectl and some other tool.

[khanhtc1202]

@ffjlabo Ofcource, we will update pipectl commands related to applications later. I just do not want to update the API this time to confuse the outer tools dev because the pipedv1 plugin is not yet ready.
Also, I don't add comments here since it's not just this API but others like AddApplication that need to be revised later, too. The change here isn't caused by an API change but by an internal store interface change, so fewer comments are okay. We have to revise all the pipette commands later, so I think a comment is not needed.

[ffjlabo]

LGTM