Node name templates

[justparking]

This allows for dynamic node naming using conventional dollar-sign substitution (i.e. $NAME or ${NAME WITH SYMBOLS}) with several useful resolution techniques.

By example, the first node created could be:
Nodel Recipes Sync for $HOSTNAME ${http port} (${os.name}, ${mac})

This would expand out to be:
Nodel Recipes Sync for MYCOMPUTER 8085 (Windows 10, fc:f8:ae:3e:5f:17)

I envisage name templates to be quite convenient when used with Computer and Application nodes.

Resolution steps in order tried:

1. if the node's signal/event is present¹, use its value (e.g. extracted device serial numbers could be used)
2. hostname¹ returns the hostname as provided by the environment²
3. IP, IP Address or IP Addresses (¹) return the IP addresses of bound interfaces
4. MAC, MAC Address or MAC Addresses (¹) return the MAC addresses² of bound interfaces
5. HTTP Port¹ returns the HTTP port of the Nodel host
6. Version¹ returns the version of the Nodel host
7. Hosting Rule¹ returns the hosting rule(s) of the Nodel host
8. try against Nodel Diagnostics values (case insensitive, see link)
9. try against system environment variables³ (see link)
10. try against Java platform system properties⁴ (see link)
    —
    ¹ case-and-symbol insensitive
    ² result is case matched according to name, e.g. MAC returns AA:BB:.., mac returns aa:bb...
    ³ on Windows, lookup is case-insensitive. Others likely case-sensitive.
    ⁴ likely case-sensitive

[justparking]

Built a related release, see https://github.com/justparking/nodel/releases/tag/feat_nameTemplates-2.2.1-rev425.

[scroix]

I missed this review before you submitted, sorry.

But I tried it out this morning and I only had a mild success.

These are based off your above example.
Nodel Recipes Sync for $HOSTNAME ${http port} (${os.name}, ${mac})

Windows 10 1909
feat_nameTemplates-2.2.1-rev425