webinterface-wifi VS webinterface-persist-ip

There's this program which will make the web interface available over wifi so you can download pdfs and upload files but its necessary to first start the web interace with the cord plugged in after turning the device on/ restarting https://github.com/rM-self-serve/webinterface-wifi.

- This program will not start/enable the web interface nor ensure that the usb interface maintains the ip 10.11.99.1 [WebInterface-OnBoot](https://github.com/rM-self-serve/webinterface-onboot) does this for version 2.10 but I do not have the newest software to test against. Using something like [webui_invincibility.sh](https://github.com/reHackable/scripts/wiki/webui_invincibility.sh) with [WebInterface-OnBoot](https://github.com/rM-self-serve/webinterface-onboot) would ensure that [WebInterface-Wifi](https://github.com/rM-self-serve/webinterface-wifi) works on boot.

While no longer enabling the web interface setting is great, the real magic is in what is now possible. The web interface keeps running when the usb cable is disconnected, which means that it still has the ability to upload and download files, there is just no way to connect to it. But now that we can ensure the web interface is always running and accessible via webinterface-onboot and webinterface-persist-ip, we can write programs that connect to the device over wifi but can still use the web interface under the hood. This is useful as uploading a file to the device most any other way will require restarting the device to see the file, and work is still being done on programs that can generate pdfs from the new file format (the web interface can). As a first step in that direction, I created..