Fix failing tests by updating field type expectations from 'number' to 'NUMBER'

[Copilot]

The convertValueToFieldType function tests were failing because they were passing the incorrect field type parameter. The function expects "NUMBER" (uppercase) but the tests were passing "number" (lowercase).

This mismatch caused four test failures:

• convertValueToFieldType converts string to number for number field
• convertValueToFieldType converts string to float for number field
• convertValueToFieldType converts zero string to number for number field
• convertValueToFieldType throws error for invalid number

The fix updates all test expectations to use "NUMBER" instead of "number", which aligns with the function's implementation that checks for fieldType === "NUMBER".

All tests now pass (30/30) and the code builds and lints successfully.

Fixes #183.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[Copilot]

Pull Request Overview

This PR fixes failing unit tests by correcting the field type parameter from lowercase "number" to uppercase "NUMBER" in the convertValueToFieldType function tests. The function implementation expects uppercase field type values, but the tests were using lowercase, causing four test failures.

• Updates test parameter values to match the function's expected input format
• Ensures all tests pass by aligning test expectations with implementation requirements

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}