IBX-8825: Added strict_mode for REST API

[Steveb-p]

🎫 Issue	IBX-8825

Description:

This PR introduces the concept of strict_mode for REST.

In strict_mode, when REST processing encounters an error/exception that it previously silenced (and usually logged as an error) it will re-throw it.

For QA:

Note

This functionality needs to be tested separately on prod and dev application environments.

Documentation:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[konradoboza]

Looks good, but I would rename it to verbose_mode maybe or silence_mode: false. Strict to me isn't that self-explanatory but it's not a blocker.

[Steveb-p]

Looks good, but I would rename it to verbose_mode maybe or silence_mode: false. Strict to me isn't that self-explanatory but it's not a blocker.

It follows a similar feature that is coming for Page Builder, and is available in Twig itself.

It's strict_mode because it converts logical errors that can be silenced on production into exceptions in dev environment. It matches PHP declare(strict_types=1); setting and JavaScripts "use strict".

Verbosity doesn't really match as we are not adding any additional info that wasn't already there. We're "promoting it" to a real exception.

[Steveb-p]

@adamwojs I'd need a decision here whether QA should test this or not.

It might be quite difficult to test, since it requires some custom field types, and missing a normalizer for it's value. WDYT?

[adamwojs]

I'd need a decision here whether QA should test this or not. It might be quite difficult to test, since it requires some custom field types, and missing a normalizer for it's value. WDYT?

We can skip QA. It's doesn't affect prod. env.

[Steveb-p]

Merged up into main in 49a2bfd.