Support ALIENWIIF1 as an separate target
This will allow to build an HEX file independently to the NAZE target

An ALIENWIIF3 may also come in the future based on STM32F303. Both
likely will share the same default settings. This is why I don’t use
ALIENWII32 as target name yet.
Merge pull request #271 from MJ666/AlienWii32_target

Support ALIENWIIF1 as an separate target