Profiler Capture Target Frame Time strips the decimal separator instead of rejecting fractional input

Steps to reproduce:

1. Create a new 3D URP project
2. Open Window > Analysis > Profiler
3. Record any data (e.g. Enter and exit Play mode)
4. Click on the save icon to save a Capture
5. In the Capture List, click the saved capture to open it
6. Click on its kebab (⋮) menu and choose Target Frame Time > Custom
7. Type 60.5 and press Enter
8. Observe the target frame time on the capture row

Actual results: The decimal point is stripped and the value is committed as 605 FPS
Expected results: The input is either rejected or rounded to a whole frame rate

Reproducible with versions: 6000.6.2f1, 6000.7.0b2

Can’t test with versions: 6000.3.24f1 (no kebab menu)

Tested on (OS): macOS 26.5, Ubuntu 24.04

Notes:

• A comma behaves identically, so this is not limited to users who type a dot: in locales where the comma is the decimal separator, entering a
  frame rate the way the locale formats it (60,5 / 59,94) silently produces the wrong value