Resolve Pitest suppression for EmptyForIteratorPadCheck

[Kevin222004]

Related to #7797

kill mutation

checkstyle/.ci/pitest-suppressions/pitest-whitespace-suppressions.xml

Line 53 in ba8efc2

<description>replaced call to java/lang/String::trim with receiver</description>

and

checkstyle/.ci/pitest-suppressions/pitest-whitespace-suppressions.xml

Line 44 in ba8efc2

<description>replaced call to java/lang/String::toUpperCase with receiver</description>

for EmptyForIteratorPadCheck

[romani]

Can we fix all similar issues at one issue and multiple PR or one PR?

[nrmancuso]

If we are only adding tests, I think it would be fine to resolve a few of these in the scope of one PR/issue.

[rnveach]

My wording to him before this issue was:

Single mutation issues was just for getting started to ensure we can confirm communication and confirm understanding of pitest and how it functions. Since this check only has 2 mutations, please just create 1 more issue of a single mutation and afterwards I think we can do multiple. However, even with multiple it is best to keep separate PRs between adding tests and changing production code. Adding tests is easier to merge then changing production code which will require a closer review and regression reports.
Beware, if PRs start to get complex we will want them split more, so I would be careful on putting too much into a single PR. It is not that much more work to create separate branches and PRs.

this check was AbstractParenPadCheck at the time.

[Kevin222004]

I have updated the pr description

[rnveach]

Fix was merged