fix(secret): Consider secrets in rpc calls

[ankk13]

Description

Currently secrets stored as part for blobInfo are dropped when putblob is done via remote cache.
The final server scan response as well drops Secrets if any.
This Pull Request, adds support to Secrets field for RPC calls

The change for pkg/rpc/client/client.go is needed as scanner/service.proto changes were not in sync.

Related issues

• Close #XXX

Related PRs

• #XXX
• #YYY

Remove this section if you don't have related PRs.

Checklist

• I've read the guidelines for contributing to this repository.
• I've followed the conventions in the PR title.
• I've added tests that prove my fix is effective or that my feature works.
• I've updated the documentation with the relevant information (if needed).
• I've added usage information (if the PR introduces new options)
• I've included a "before" and "after" example to the description (if the PR is a user interface change).

[knqyf263]

I tested this PR, but didn't see secrets in client/server mode. I didn't take a deeper look though. Could you add a test here so that we can confirm secret scanning works in client/server mode as well?
https://github.com/aquasecurity/trivy/blob/main/integration/client_server_test.go

You can put dummy secrets under testdata and detect them in fs scanning.

trivy/integration/client_server_test.go

Lines 232 to 240 in da6f1b6

	{
	name: "scan pox.xml with fs command in client/server mode",
	args: csArgs{
	Command: "fs",
	RemoteAddrOption: "--server",
	Target: "testdata/fixtures/fs/pom/",
	},
	golden: "testdata/pom.json.golden",
	},

[knqyf263]

Can we use the same golden file? We need to make sure the results are the same between standalone mode and client/server mode. For example, we use the same golden files for image scanning.

trivy/integration/client_server_test.go

Lines 49 to 55 in 85ca86c

	{
	name: "alpine 3.9",
	args: csArgs{
	Input: "testdata/fixtures/images/alpine-39.tar.gz",
	},
	golden: "testdata/alpine-39.json.golden",
	},

[knqyf263]

Do you have any specific reason to add this key? This test case already has GitHub PAT and AWS access keys. Aren't they enough?