[fix](test) Remove wrapper_field dependency from unit tests (#60530)

[Gabriel39]

Update FromStringTest, TextSerde, and CsvSerde unit tests to remove dependency on the deleted wrapper_field.h header. Replace WrapperField usage with hardcoded min/max values for IP addresses and direct string comparisons for other types. Test logic and coverage are preserved.

• Remove wrapper_field.h includes
• Replace WrapperField::create_by_type() and related calls with explicit values
• Update test data structures to remove wrapper field expectations
• Simplify nullable string tests to use test string directly
• Update comments to reflect serde-only testing approach

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

None

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:

• This is a refactor/code format and no logic has been changed.
  - [ ] Previous test can cover this change. - [ ] No code files have been changed. - [ ] Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.

• Yes.

• Confirm the release note

• Confirm test cases

• Confirm document

• Add branch pick label

---

What problem does this PR solve?

Issue Number: close #xxx

Related PR: #xxx

Problem Summary:

Release note

None

Check List (For Author)

• Test

  • Regression test
  • Unit Test
  • Manual test (add detailed scripts or steps below)
  • No need to test or manual test. Explain why:
    • This is a refactor/code format and no logic has been changed.
    • Previous test can cover this change.
    • No code files have been changed.
    • Other reason

• Behavior changed:

  • No.
  • Yes.

• Does this need documentation?

  • No.
  • Yes.

Check List (For Reviewer who merge this PR)

• Confirm the release note
• Confirm test cases
• Confirm document
• Add branch pick label

[hello-stephen]

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
3. What features were added. Why was this function added?
4. Which code was refactored and why was this part of the code refactored?
5. Which functions were optimized and what is the difference before and after the optimization?

[Gabriel39]

run buildall

[Gabriel39]

run buildall

[Gabriel39]

run buildall

[Gabriel39]

run buildall

[doris-robot]

BE UT Coverage Report

Increment line coverage 16.30% (22/135) 🎉

Increment coverage report
Complete coverage report

Category	Coverage
Function Coverage	53.00% (19110/36054)
Line Coverage	36.18% (177947/491881)
Region Coverage	32.76% (137845/420716)
Branch Coverage	33.68% (59759/177410)