Move role config to Function manifest instead of Piped manifest

[khanhtc1202]

What this PR does / why we need it:

The role parameter passed to Create/Update Lambda application is the role set for the deploying lambda function (service role), not for the running agent (user role) to deploy it. So, I think it should be a part of FunctionManifest instead of CloudProviderConfig as the current design.

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

NONE

[pipecd-bot]

Code coverage for golang is 33.83%. This pull request increases coverage by 0.01%.

File	Function	Base	Head	Diff
pkg/app/piped/cloudprovider/lambda/function.go	FunctionManifestSpec.validate	80.00%	71.43%	-8.57%
pkg/app/piped/cloudprovider/lambda/client.go	client.Apply	0.00%	0.00%	+0.00%

[nakabonne]

/lgtm

[pipecd-bot]

Code coverage for golang is 33.83%. This pull request increases coverage by 0.01%.

File	Function	Base	Head	Diff
pkg/app/piped/cloudprovider/lambda/client.go	client.Apply	0.00%	0.00%	+0.00%
pkg/app/piped/cloudprovider/lambda/function.go	FunctionManifestSpec.validate	80.00%	71.43%	-8.57%

[nghialv]

Nice. Thank you.
/approve

[pipecd-bot]

This pull request is APPROVED by nghialv.

Approvers can cancel the approval by writing /approve cancel in a comment. Any additional commits also will change this pull request to be not-approved.