Base_Engine: Centralisation and Standardisation of errors, warnings and notes

[rwemay]

Description:

Sorry if this has already been raised elsewhere(!!) Having just made up another warning text, I've been thinking for a while it could be useful to standardise some common warnings into a format - e.g. IsNurbsCurve or IsPlanar, concatenating (or not depending what the format(s) we decide) things like the guid.

[adecler]

Adding on this issue to broaden the spectrum to a general redesign of the error recording solution.

From the discussion we had in the Monthly Framework Planning Session :

We need to improve the logging system to allow for example to
- silence it
- throw exceptions instead of logging errors when RecordError is called
- be very careful on how the interaction of global settings work on the stack
- also idea of bookmark to delete or recover records since the time of the bookmark
- @alelom to raise issue and draft PR to cover his own user case that triggered the discussion

@alelom , see the change of this PR that was a temporary and bad solution for the problem you raised here about silencing the logging system temporarily. So something that is probably worth mentioning in the issue you raise as both an example of the problem we need to solve and something to fix in the long run once we have a better solution in place.

I would also add that we also mentioned migrating the error log out of Reflection and into the Base namespace.

[adecler]

See ##1645 for reference to teh migration of some of the reflection engine to the base engine