fix(k8s-gke): skip flush and reshard nemesis due to the bug

[vponomaryov]

Cause: scylladb/scylla-operator#1077

PR pre-checks (self review)

• I followed KISS principle and best practices
• I didn't leave commented-out/debugging code
• I added the relevant backport labels
• New configuration option are added and documented (in sdcm/sct_config.py)
• I have added tests to cover my changes (Infrastructure only - under unit-test/ folder)
• All new and existing unit tests passed (CI)
• I have updated the Readme/doc folder accordingly (if needed)

[vponomaryov]

Failed job with enabled nemesis is here: https://jenkins.scylladb.com/view/staging/job/scylla-staging/job/valerii/job/vp-longevity-scylla-operator-3h-gke/12/consoleFull
Passed job with the skipped nemesis is here: https://jenkins.scylladb.com/view/staging/job/scylla-staging/job/valerii/job/vp-longevity-scylla-operator-3h-gke/15/consoleFull

[fgelcer]

@vponomaryov , good practice is to give the bug a number, so we can track backwards, once the bug will be fixed

[fruch]

@vponomaryov , good practice is to give the bug a number, so we can track backwards, once the bug will be fixed

it's written in the code:
scylladb/scylla-operator#1077

[vponomaryov]

@vponomaryov , good practice is to give the bug a number, so we can track backwards, once the bug will be fixed

As @fruch has already mentioned, the bug is referenced in the code change. So, good practice has been applied here from the start.

[fruch]

Having it also int the commit message and PR description could be even better, i.e. getting it linked to the bug.