Add ENABLE_CACHE_MUTATION_DETECTOR=true for gcp gci e2e default and alpha test suites

[Rajalakshmi-Girish]

Making the ENABLE_CACHE_MUTATION_DETECTOR=true for all the marker jobs of default test suite in https://github.com/kubernetes/test-infra/blob/master/releng/test_config.yaml.

Also enabling this env for alpha feature jobs for master branch in https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml

This is being done to make master branch jobs and release branch jobs have the same set of parameters.

[dims]

cc @aojea

[aojea]

/lgtm

[dims]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, Rajalakshmi-Girish

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/generated/OWNERS [dims]
• config/jobs/kubernetes/sig-cloud-provider/OWNERS [dims]
• releng/OWNERS [dims]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

@Rajalakshmi-Girish: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key generated.yaml using file config/jobs/kubernetes/generated/generated.yaml
• key gcp-gce.yaml using file config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml

In response to this:

Making the ENABLE_CACHE_MUTATION_DETECTOR=true for all the marker jobs of default test suite in https://github.com/kubernetes/test-infra/blob/master/releng/test_config.yaml.

Also enabling this env for alpha feature jobs for master branch in https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes/sig-cloud-provider/gcp/gcp-gce.yaml

This is being done to make master branch jobs and release branch jobs have the same set of parameters.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.