The interruption handling function and the pin that was being configured
as interruption were wrong

Temporary solution for testing the RTM SFP board

A user defined funtions was also implemented in order to initialize all
wanted sensors in the board

Now it's easier to select the clock connections based on the board
hardware.

The board port should not own a module implementation, rather it should
only select which one will be used.

The driver shouldn't need a FreeRTOS definition to work properly, just
use the 32-bit variable to count the ticks, it should be enough

Move all files that are board specific to a new folder in 'port/'

Insert comments in-line to ease future changes

This i2c.* files were just holding some helper functions, like a I2CInit
wrapper and GA discovery.
Just move these function to their right places

This flag should be set to compile the firmware to run the first time on
the board, since it'll write the EEPROM with the board ID

There's a Reset IC in the AFC Board that only releases the clock switch
(ADN4604) reset pin only ~140ms after the P1v0GOOD signal goes high

If we only check the sensor state flag, when a abrupt shutdown occurs,
we'll have to run through the sensor event state machine at least 2
times before achieving a state that causes the P12vGOOD flag to be
cleared.
Since the payload task runs at a greater frequency than the sensors',
it'll try to power-up the payload again based on the erroneous sensor
state

There's a drop in the voltage between the standalone voltage entry and
the value measured at the INA220, which is about 0,6~0,8v, this was
causing the board to always stay between Low-crit and Low-noncrit state.

Reset the power good flags to avoid the state machine to start over
without a new read from the sensors.
This was causing the payload to quickly turn on after a QUIESCE event,
since the INA220 sensor task task a little longer to update all the
sensors readings.
Fixes #23