[Feature] Top_P

- Why we are not using 2 decimal instead of 1 i mean like **Top_p 0.95**
- Sorry, I'm not good at TypeScript.
```

{
props.updateConfig(
(config) =>
(config.top_p = ModalConfigValidator.top_p(
e.currentTarget.valueAsNumber,
)),
);
}}
>

Start at the TopP settings control shown in the issue, which uses ListItem, InputRange, and props.modelConfig.top_p. Check how the current value is displayed and verify manually that values such as 0.95 retain two decimal places while the range still accepts 0.01 steps.

Written by the indexing model from the issue text.