BHoM_Engine: provide exception based on property "path"; wildcard support

[alelom]

Description:

As described in BHoM/BHoM#1084.

Evaluate whether to do this

1. using a boolean or enum toggle (to choose between specifying simple property name e.g. X or the "path" or "path with wildcard"
2. having separate inputs for "propertyNameExceptions" (disallow paths and wildcards) and "propertyPathExceptions" (that disallows simple property name, could allow for wildcards)
3. simply checking the exception case by case (does it contain a . ? Then it is a "path". Does it contain a *? Then use wildcardPattern).

(1) may sound as having more control over things, but you may want to actually avoid pushing the responsibility of the choice of logic on the user, because we can find a way to automate it as in (2) and (3), so I would avoid it probably.

Probably case (3) might be the simplest to use, but could have performance hit depending on implementation.
To minimise performance hit, we could use (3) at the level of the ComparisonConfig, but then split the exceptions in three separate lists to be passed separately to DefiningString (which basically means (3) in the front-end and (2) in the back-end). This way, DefiningString() would avoid the responsibility of checking what type of exception is every time, reducing the performance hit.