Save fails silently when the value of a property of an object cannot be parsed properly

This behaviour was introduced by XWIKI-1491 in order to palliate the "ugly" exception displayed on the screen on such a save, but the resulted behaviour is completely WTF for regular users, see also XWIKI-18971 .

How to reproduce:

• create an application with a number field, for example floating point (but can also be integer)
  • the Movies application shipped in the Help app of the standard distribution can be used, the "runtime" property
• in the form of a page, type something that is not a number or a number in a 'wrong' format - for example, use a whitespace for thousands separator, like this: "1 000"
• save

Actual result:

• the save goes through, there is no error, however the number property is not updated at all on the existing page
• all other properties changed in the form are saved fine
• the user may not realize that one of the properties was not actually saved.

Expected result:

• there should be some form of information that the save has failed.

Note:
This is particularly bothering for in place properties editing (added by XWIKI-17213), which will fail to save a single value without any information about why the save didn't work or even that it didn't work.