fix(cache-issues): grant read permissions for sc-dbaas-data-qa account

[mikliapko]

Since SCT test can be triggered not only from under cloudius-systems, but sc-dbaas-data-qa account (cloud longevity tests), cache-issues job is adjusted to grant read permissions to the uploaded files for this sc-dbaas-data-qa account.

Grants for cloudius-systems account should be specified as well, otherwise, the owner will miss these permissions.

Testing

• Local test

mikita@mikita-pc:~$ aws s3 cp test.txt s3://scylla-qa-keystore/test.txt --grants read=id=ae6058f752268a384a1a3e3732c4eea3d8a7d597e9cbc7f5bd7b791a224f3e67 full=id=0c2716c5c3e86717000f7af99a8c82c5f776b86179f73d4985de88ceff86a9a4
upload: ./test.txt to s3://scylla-qa-keystore/test.txt

• GH Actions job, created files in test directory

PR pre-checks (self review)

• I added the relevant backport labels
• I didn't leave commented-out/debugging code

[mikliapko]

@fruch
I saw you mentioned that this job can't be tested from forks (I suppose because of secrets).
How can I do a verification run?
And should I assign any backport label? I suppose not.

[fruch]

Lets put those into secrets

[mikliapko]

Don't have permission to manager secrets here.
Could you please help with that?

[fruch]

I've created secrets with those names

[fruch]

@fruch
I saw you mentioned that this job can't be tested from forks (I suppose because of secrets).
How can I do a verification run?
And should I assign any backport label? I suppose not.

You can push it to the main repo for testing, I think you should have permission for doing that.

[mikliapko]

@fruch
I saw you mentioned that this job can't be tested from forks (I suppose because of secrets).
How can I do a verification run?
And should I assign any backport label? I suppose not.

You can push it to the main repo for testing, I think you should have permission for doing that.

Okay, I'll check

[mikliapko]

@fruch
I saw you mentioned that this job can't be tested from forks (I suppose because of secrets).
How can I do a verification run?
And should I assign any backport label? I suppose not.

You can push it to the main repo for testing, I think you should have permission for doing that.

Okay, I'll check

Did a testing here - GH Actions job, created files in test directory.

[fruch]

LGTM