CHIRP

I am working with the F4HWN firmware team to get their driver into a standard CHIRP format to support the F4HWN firmware which has significant additional development beyond the latest Egzumer firmware which it was forked from. I will aim to keep this issue updated with the latest developments on the driver.

The firmware is here: https://github.com/armel/uv-k5-firmware-custom
Chirp driver is here: https://github.com/armel/uv-k5-chirp-driver
Chirp driver development issue is here: https://github.com/armel/uv-k5-chirp-driver/issues/58

At the time of writing the latest F4HWN firmware & associated CHIRP driver version is 4.0.0

I understand the list of things which need to be done to adapt the current CHIRP driver into one that is in a format that CHIRP core developers would consider the minimal acceptable structure to be considered (and that right now it won't be considered), e.g. from comments on #11270.

This new issue is required to allow me to load the module into CHIRP without having to copy files directly into the CHIRP installation after each upgrade. If there is a better way to manage that please let me know.