Fix numerical person properties turning to strings on save

[yakkomajuri]

Changes

Please describe.
If this affects the frontend, include screenshots.

Close #3189

Tagging you @paolodamico because I wonder when we'll be releasing persons-2353. I'm not the biggest fan of all the UI updates but just the new logic is almost a necessity.

Spent more time than I'd like working on the old persons "logic" and decided it wasn't worth it from a prioritization standpoint.

Hence this fixes the logic on PersonV2 as I imagine we'll roll out the logic updates even if the experiment turns out bad from a UX perspective.

Checklist

• All querysets/queries filter by Organization, by Team, and by User
• Django backend tests
• Jest frontend tests
• Cypress end-to-end tests

[paolodamico]

Great stuff, lgtm! Did a minor change so that we attempt to parse as number based on the new input not the old value. Please review before merging.

[paolodamico]

In a more general sense, I'll definitely check for the release of persons-2353 this release cycle. Regardless I think it's definitely worth that you comment on the UI stuff that you don't like / would improve so we can work on those too if we do release it (#2353 or feel free to open a new issue).

[yakkomajuri]

makes sense, cheers!