Define new ping ID handling methods

[manishmeganathan]

• Allow poll IDs to be sent by the control command
• Define a format that allows poll IDs to be differentiated based on the origin. (from within the mesh or from the controller)

[manishmeganathan]

Rename the poll ID keys to ping ID across the library

[manishmeganathan]

New ping ID format

All ping IDs will be treated as strings across the entire stack.

userping-<custom phrase> - For pings triggered from the CLI.
sensorping-<timestamp> - For sensor pings triggered by the scheduler.
configping-<timestamp> - For config pings triggered by the scheduler. controlping-<random 6 digit numeric> - For pings triggered by the control node pinger button.
remoteping-<random 6 digit numeric> - For pings triggered by a sensor node pinger button.

Note: controlpings and remotepings are usually only going to be sensor data pings. While the implementation for them exists in the 'readconfig' handlers, there is currently no hardware configuration that supports this trigger. This implementation is more for uniformity and may be given hardware support down the line.

[manishmeganathan]

Adopt a new ping standard buttonping-<6digit>-mesh for all button based pings. control or remote. controlping-<origin phrase>-<timestamp>-mesh for controller pings for the whole mesh controlping-<origin phrase>-<timestamp>-node for controller pings to a specific node userping-<phrase>-mesh for user pings to the whole mesh userping-<phrase>-node for user pings to a specific node