add shouldnot to codespellignore

[jackfrancis]

What type of PR is this?

/kind failing-test

What this PR does / why we need it:

I have definitive evidence that I work for codespell and not the other way around.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

• squashed commits
• includes documentation
• adds unit tests

Release note:

NONE

[CecileRobertMichon]

Error: ./.codespellignore:7: ShouldNot ==> should not, shouldn't

hmmmm what?

[CecileRobertMichon]

could you try changing this to

Suggested change

	ShouldNot
	shouldnot

Seems that there is a known bug where it only wants lowercase codespell-project/codespell#2451 (comment)

[jackfrancis]

that works!

[jackfrancis]

@CecileRobertMichon you have my permission to admin merge this if you're looking for more GitHub badge achievements

[CecileRobertMichon]

/lgtm
/approve

This fixes it for now. Let's follow up on

1. Why ShouldNot is getting flagged, it's a common testing word and is a regression in the latest codespell release IMO
2. Whether we think there is value in keeping codespell enabled in general

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon

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:

• OWNERS [CecileRobertMichon]

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

[jackfrancis]

/cherry-pick release-1.5

[k8s-infra-cherrypick-robot]

@jackfrancis: #2728 failed to apply on top of branch "release-1.5":

Applying: add ShouldNot to codespellignore
Using index info to reconstruct a base tree...
M	.codespellignore
Falling back to patching base and 3-way merge...
Auto-merging .codespellignore
CONFLICT (content): Merge conflict in .codespellignore
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 add ShouldNot to codespellignore
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.5

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/test-infra repository.