TranslateBrowsePath should always manage exact ReferenceTypeId
When SOPC_HAS_SUBTYPE_HYBRID_RESOLUTION server option is unset (default) to use only well known types for type resolution mechanism, all reference types out of OPC UA namespace (NS0) or in NS0 with NodeId > 1000 (default NS0 subtype hierarchy cache size: see ./scripts/generate-embedded-base-type-info.py) subtype relation will not be resolved.
In this mode resolving subtype relations only for well known types, the service TranslateBrowsePath was still failing to resolve a path element (which contains a ReferenceTypeID out of the subtype hierarchy cache) even if the source node has this exact reference defined in its references. This behavior was not expected since it requires no type resolution in this case.
This is due to the fact a ReferenceTypeId out of the subtype hierarchy cache was always considered as invalid in this mode whereas we should only check the NodeId matches a node of class ReferenceType.