Issues with historical Wigle uploads after boot count reset

[pejacoby]

See #154 - after doing a factory reset the boot counter is reset. New files may be created with names that match existing Wigle uploads, resulting in them not being uploaded when Wigle is checked in the auto-upload process.

The 'new' file numbers may overlap with uploads from a long time ago, so Wigle is returning status to the auto-upload process indicating it already has the file. As a result no upload occurs. Screenshot attached of two runs shortly after a factory reset.

The first run was an hour walk with a file size of 310kb. Obviously there are more than "0 total" APs in this file -- no upload was attempted after a reboot.

The second file is from a quick reboot where I let everything fire up and start scanning, then shut down. Here too the file size and WiFi total count don't make sense -- 2kb file yes, but containing 3157 APs is unlikely. Again no upload attempted here on the reboot.

Previous files since the factory reset auto-uploaded but I'm guessing that is because there was no matching filename found in the call to Wigle.

As you noted in #154:
This appears to be a separate issue. If I'm understanding correctly, it seems the wardriver is not correctly matching local files with files which WiGLE has. This is meant to be achieved with 3 variables: The wardriver hardware ID, the bootcount value, and the filesize. These matching by coincidence is unlikely so it seems there is a bug in the implementation.