Support Property in out on core nodes

[Steve-Mcl]

Types of changes

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

Proposed changes

In alignment with proposals in #4651:

• Adds "Property Out" field where sensible
• Updates "Property In" field to clarify input/output

Nodes Updated:

In the format proposed by #4651, the name field was moved to the top, the input property is next and the new (or existing) output property was placed at the end (or at the end of main properties / above the <hr> and advanced properties in some nodes)

TODO:

• Post before and after screenshots in the issue for evaluation and agreement
• Write tests for affected nodes.
  • Where applicable, tests should set property and verify the input data should be taken from the correct msg property
  • Where applicable, tests should set propertyOut and verify the results go to the correct msg property
• Update built in help for affected nodes
• Switch PR out of draft

Checklist

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