test: updated 3 tests in StringUtilsTest to use parameterized

[Monilnarang]

• I have registered the PR changes.

Ⅰ. Describe what this PR did

Summary:

• Parameterized tests : testIsNullOrEmpty, testIsBlank, testIsNotBlank

Elaboration:

• The same method calls (isNullOrEmpty, isBlank, isNotBlank) were repeated multiple times with different inputs, making the test harder to maintain and extend.
• When a test fails, JUnit only shows which assertion failed, but not which specific input caused the failure.
• Adding new test cases requires copying and pasting another block of statements instead of simply adding new data.

To accomplish this, I retrofitted these tests into a parameterized unit test. This reduces duplication, allows easy extension by simply adding new value sets, and makes debugging easier as it clearly indicates which test failed instead of requiring a search through individual assertions.

Test execution results after changes:

Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?

Ⅳ. Describe how to verify it

Successful tests run

Ⅴ. Special notes for reviews

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 54.30%. Comparing base (0495f83) to head (13d0ee9).
Report is 1 commits behind head on 2.x.

Additional details and impacted files

@@             Coverage Diff              @@
##                2.x    #7295      +/-   ##
============================================
+ Coverage     54.26%   54.30%   +0.03%     
- Complexity     7267     7271       +4     
============================================
  Files          1178     1178              
  Lines         41962    41962              
  Branches       4923     4923              
============================================
+ Hits          22772    22786      +14     
+ Misses        17038    17022      -16     
- Partials       2152     2154       +2     

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[slievrly]

@Monilnarang Pls resolve conflicts.

[Monilnarang]

Done!

[slievrly]

LGTM