Add log command to set log url to path

[hansr]

A key feature of the ZTNA system is to view device logs.

Every ZTNA perimeter will have a log path created and a tag generated that enables logs to the URL. If the parameter is specified and the URL is valid, logs should be flowed also to the URL.

If they are flowed to the URL, don't cease flowing logs also to the existing paths.

Syntax:
diode -logurl=[url]

This should also be added to the join command batch processing.

The CLI will auto-generate CLI logs to the URL if specified. We should also support -applogports=app1name:1001,app2name:1002,appnname:1003

Add log details to the localhost API

TODO: If we suport applogports -> how will an app specify on command line / systemd to pipe log output there? What json embellishment will we add to the data coming into the port so that the logging server has contextual info on the various app logs.

The logging server will deny logs from clients that are not part of the perimeter's fleet. Perimeter is reported as part of the JSON log and is used to route logs to the correct perimeter.

HANS: Review fleet / perimeter delineation in the billing -> ideally we can suppress "fleet" and everyone only knows about perimeters. Must fold in the existing fleets??? Maybe rename them to perimeters??