fix: Update container delete grace period to match Kubernetes default

[matveybrant]

Per https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/#pod-v1-core the default pod grace period is 30 seconds, so I believe this should match per the comment.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this is a chore.
• The title of the PR is (a) conventional, (b) states what changed, and (c) suffixes the related issues number. E.g. "fix(controller): Updates such and such. Fixes #1234".
• I've signed the CLA.
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My builds are green. Try syncing with master if they are not.
• My organization is added to USERS.md.

[simster7]

I doubt we'll want to change this number as a whole. We'll probably want to parametrize this.

[matveybrant]

I agree that we should parameterize it, but in the mean time I thought it would make sense to at least set it to match the kubernetes default

[simster7]

@jessesuen had also mentioned he expected this value to be 30 seconds. I'll bring it up with him

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

0.0% Coverage
0.0% Duplication