IfcElements PredefinedType note contradicting Object Predefined Type concept

Note on IfcWallType ([ref](https://ifc43-docs.standards.buildingsmart.org/IFC/RELEASE/IFC4x3/HTML/lexical/IfcWall.htm)):

So even if `IfcWallType.PredefinedType == NOTDEFINED`, then `IfcWallType.PredefinedType` takes priority over `IfcWall.PredefinedType` and OJT001 should error:

https://github.com/buildingSMART/ifc-gherkin-rules/blob/7d2a5ffdc24dd86f40b2c64f549e10372721f76c/features/rules/OJT/OJT001_Object-predefined-type.feature#L22-L27

But Object Predefined Type concept ([ref](https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/concepts/Object_Attributes/Object_Predefined_Type/content.html)) states that:

So it does allow using `IfcWall.PredefinedType` if `IfcWallType.PredefinedType == NOTDEFINED`.

So in theory note on IfcWall page should be:

> NOTE The _PredefinedType_ shall only be used if no _IfcWallType_ is assigned, or if _IfcWallType.PredefinedType_ is set to _NOTDEFINED_, in which case _IfcWall.PredefinedType_ takes priority.

Start with the linked IfcWall documentation note, the Object Predefined Type concept, and features/rules/OJT/OJT001_Object-predefined-type.feature lines 22-27. Confirm that the wording and rule expectation agree on behavior when IfcWallType.PredefinedType is NOTDEFINED; done means the contradiction is resolved consistently.

Written by the indexing model from the issue text.