Introduce timezone, detailedDataSecondsEnabled and detailedDataHoursEnabled

[cdolghier]

This MR:

introduces detailedDataSecondsEnabled and detailedDataHoursEnabled

These are configuration options to selectively disable either hourly or per-second data collection. The reasoning is that collecting per-second data is expensive for both Emporia servers and the user (storage-wise and CPU-wise for underpowered shared servers). I run the script on an underpowered Intel Atom J4125 and the once-hourly fetch of 3600 datapoints per channel is a 10second x 50% CPU for data I don't need.

introduces timezone

This is a configuration knob to configure the timezone for the calculation of "end of day". Although it is strictly speaking not necessary, as the same end effect can be achieved via configuring the host system and/or Docker container, the preexisting way of doing things has certain disadvantages:

• for the Docker container, it is highly unlikely for the average user to be in UTC timezone. Therefore everyone gets silently incorrect (truncated) counters for the daily counters and discovering the erroneous data and its root cause is a frustrating process
• for the native deployment, the server timezone will usually be the correct timezone, but for cases where it isn't one needs to override the "server timezone" for one process in the system.

IMO it's just cleaner to make the account timezone a native functionality of the script.

updates the documentation

Easy-peasy update to README and json.sample files to reflect the above.

Add some whitespace around = in preexisting code to make it consistent with surroundings.

[jertel]

Very nice contribution here, thanks for continuing to improve this project. Please add the new features to the CHANGELOG.md and follow the pattern I started in the 1.6.1 release. You can add them to the TBD section since the next version number hasn't been selected yet.