EZP-21109: Changed default values for min and max to null

> Fixes https://jira.ez.no/browse/EZP-21109

## tl;dr;
The previous defaults `0` and `false` were converted to the integers `0` and `0`, resulting in `0` being the only valid value for the given integer field.

## Details

When creating a new Integer field without defining a `minIntegerValue` and/or `maxIntegerValue` validator constraint, the default values are used, until this PR `0` (min) and `false` (max). When those values end up in the database, they are converted to integer values, resulting in `0` (min) and `0` (max).

With this configuration, the only valid value to enter in such an integer field would be `0`.

The default behavior when creating the same field in the admin interface is to keep the both values unset by default, allowing every integer value to be valid.

This change ensures this behavior.

Cheers
:octocat: Jérôme
I should have added ", but you newer know" :). I wasn't sure if there could be an edge case in which the content type could be tried to deleted without being there, so the `try … catch` was just to make sure that the unit tests don't break at any time because of an uncritical problem.