NAS-129794 / 24.10 / Use pre-defined constant for UID validator

[anodos325]

We shouldn't have second definition of TRUENAS_IDMAP_DEFAULT_LOW.

[bugclerk]

Jira URL: https://ixsystems.atlassian.net/browse/NAS-129794

[themylogin]

Changing it there will retroactively change API definition for already released APIs, that should not be the case.

If it is not a part of API definition, let's validate it in the code, not in the API definitions,

[anodos325]

Changing it there will retroactively change API definition for already released APIs, that should not be the case.

If it is not a part of API definition, let's validate it in the code, not in the API definitions,

Obviously if someone is changing constants they'll need to be aware of its impact on other areas of the product. I don't see any reason to legitimately allow different ID ranges based on which endpoint an API consumer chooses to use.

[themylogin]

if someone is changing constants they'll need to be aware of its impact on other areas of the product.

We took an obligation to have backwards-compatible API. One of the methods we decided to use in order to comply with it is to never import anything in the API definition.

This value should probably be validated in the create/update method itself, not in the API schema.