Create system profile concept

[jakerye]

Each system has a sensible and actuatable range for each environmental variable tied to the physical system...sensors have a range and accuracy...actuators have a limited amount of energy and a limited ability to realize physical conditions in a box...It'd be great to explicate these for a number of reasons.

The biggest reason is probably for selecting / verifying recipes...for example if a recipe calls for co2 dosing but the system doesn't have a co2 doser...the user should be notified..same with temperature, same with light, etc.

This also touches on the idea of forking recipes so that they become actuatable on the system..but this topic is for another issue..and probably doesn't belong on the device ui (at least not exclusively).

Another reason to have system profiles is for selecting chart ranges. see #70

[jakerye]

exploring method in cultivation-zone branch

[jakerye]

this is going to need a coordinated effort with the cloud architecture to figure out how we represent a "cultivator" entity (e.g. multiple devices can be a part of a cultivator)...can a cultivator have multiple environments? standardized language and and cohesive vision are required to implement this successfully.