[ENHANCEMENT] Configuration of anomalous faults

[linguini1]

Please note that this issue is dependent on the completion of #36.

Problem

Packets are received very frequently and are subject to interference/noise, which may result in corrupted measurements being received. This will trigger anomalous fault detection incorrectly.

Additionally, what is considered an anomalous measurement for Spaceport might not be anomalous at Launch Canada (i.e. a temperature of 50 degrees Celsius on the launch pad at Spaceport is expected).

Proposed Solution

The threshold at which an anomalous fault is reported should be configurable, both in the value considered anomalous and how many packets within that range need to be received before a warning is issued.

For instance, this configuration for temperature at Spaceport (inside spaceport.json) says that a warning should be issued if at least 3 packets in a row are received which report a temperature lower than 10C or higher than 60C.

{
  "measurement": "temperature",
  "range": [10, 60],
  "packet_min": 3,
}

Additional Context

This configuration file's path should be able to be provided via both command line options or within the config.json file. Any config file provided over command line arguments will be used over the one within config.json.

The reasoning for a separate config file is to have different presets for each different competition/launch setting.