fix node validation to be applied to config node

[HiroyasuNishiyama]

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Proposed changes

After introduction of PR#3304, when deploying a new dashboard flow, the following warning is displayed.

This is because node validation does not apply to certain config nodes (ui_base in this case).
This PR try to fix this problem.

Checklist

• I have read the contribution guidelines
• For non-bugfix PRs, I have discussed this change on the forum/slack team.
• I have run grunt to verify the unit tests pass
• I have added suitable unit tests to cover the new/changed functionality

[coveralls]

Coverage remained the same at 67.313% when pulling dc73997 on node-red-hitachi:fix-config-node-validation into 5293563 on node-red:master.

[Steve-Mcl]

node.hasOwnProperty should be replaced with Object.prototype.hasOwnProperty.call(node, "valid")

This is the recommended form of testing for a property that avoids errors if the object has no [[Prototype]] chain

[HiroyasuNishiyama]

Thank you for your suggestion.
I fixed it not to use hasOwnProperty. However, I feel that Object.prototype.hasOwnProperty.call (node," valid ") is too long 😵‍💫 so I adopted undefined check.
It would be nice to have a utility such as RED.util.hasOwnProperty.

[knolleary]

node.hasOwnProperty should be replaced with Object.prototype.hasOwnProperty.call(node, "valid")

It will depend on where the object has come from. If it is one we are creating, then we know it has a prototype because we don't create null objects. In this instance, we know node is vanilla JavaScript Object that has been generated by JSON.parse().