Form Field: Better documentation of the behavior of a numeric field

[Fuzzy3]

Which issue does this PR close?

This PR closes #2362, closes #2887

What is the new behavior?

None. This updates the documentation on the cookbook.

Does this PR introduce a breaking change?

• [ ] Yes
• [x] No

Are there any additional context?

This PR is a different approach than the earlier PR: #3065, where instead of trying to solve the problem programmatically, we accept that browsers have their own behaviour regarding numeric fields.

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Reminders

• [ ] Make sure you have implemented tests following the guidelines in: "The good: Test".
• [ ] Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).

Review

• [ ] Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
• [ ] Do a self-review.
• [ ] Request that the changes are code-reviewed
• [ ] Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)

When the pull request has been approved it will be merged to develop by Team Kirby.