Get the uMWC yocto build to work out of the box

[shankari]

There are many changes that we can/should make to the custom Yocto image to have it work more smoothly out of the box. Recording them here so we can change the build appropriately...

1. Make sure that the image has an editor (basic vi is enough) to make it easier to view and edit configs

2. Ensure that the config directory has working configs pre-loaded, so that we don't have to download configs from your repo
   I am thinking that we want at least three parameters:
   a. AC vs DC
   b. YetiSimulator versus JsYetiSimulator
   c. MaEVe versus CitrineOS

   That should give us $2^3 = 8$ config files, all of which should at least launch properly on the Raspberry Pi
   As we work through testing on the SIL and the codebase gets more mature, we should be able to collapse (b) and (c). But we may add additional configs for new features, so we will likely still end up with three parameters:
   a. AC vs DC
   b. ISO -2 vs -20
   c. OCPP 2.0.1 vs 2.1

   I sent several of the configs that I modified on the fly at Testival to @catarial as examples. Note that:
   a. For the AC configs, ac_enforce_hlc: true should be set; otherwise the uWMC does not do HLC for AC, at least it didn't when testing

3. I am consistently unable to connect to the internet from the uMWC without manually mucking around with the routing table. We need to be able to connect to the internet if we connect to an third-party (non-open-source) CSMS that is not running on our laptop. And the weird thing is that the routing changes needed seem to be different every time.
   a. at plugfest, these were the changes needed 🔭 uMWC setup tips and tricks #110 (comment)
   b. at Testival, there was no additional 192.168.1.1 gateway, but I had to delete the existing route to 172.20.10.1

4. the logs are stored in a temporary location (/tmp) which are deleted on reboot. This is terrible design because then if the power connection jiggles a bit during charging, all the logs are gone. We should create a persistent directory for the configs, and all the configs should store them there. Note that the configs that I sent to @catarial after Testival should already have this change, but we should ensure that any new configs that we create should have them preconfigured as well.

5. install the version of less that supports -R (aka raw control characters). If we can redirect the console output, it is colorized so very hard to use with regular less and scroll up and down
   https://superuser.com/a/117842

6. set up the packet sniffing to save the key for encrypted sessions by default so that we can debug all the PKI stuff properly

Stretch goal: easier configuration of the WPA. I saw that @catarial added some CLI-based instructions (https://github.com/catarial/meta-charin-demo/?tab=readme-ov-file#connecting-to-wifi). I also have easier instructions (wpa_passphrase) to get the PSK from the passphrase, but it still requires connecting with the ethernet interface every time we want to reconfigure. When I was at Testival, if I tried to connect to the conference WiFi, but if the connection was successful, there would not be any way for me to see what the IP address was!
(my connection would be dropped and I can't see the list of connected devices on the conference WiFi)

I am not sure what is the best way to configure it without connecting via ethernet unless we can configure a UI. I am not sure how complex it would be to write a simple UI that allows us to configure from the touchscreen instead?!