fix: Begin splitting uses of wpad-wolfssl and wpad-mesh-wolfssl

In commit b46bf38e8 ("feat: Configure network-specific packages"), we
left a mistake, having the package_wpad_mesh configuration setup
actually install wpad-wolfssl as opposed to
wpad-mesh-wolfssl (probably after discovering that wpad-mesh-wolfssl
wasn't sufficient for some purpose or other).

wpad-wolfssl is a feature superset of wpad-mesh-wolfssl, but we'll
want to separate these two sets slowly if we can.

inventory.yml

@@ -17,6 +17,17 @@ templates:
     - name: wpad-wolfssl
       state: present
 
+  # Note: This is intentionally a duplicate of package_wpad_mesh --
+  # need to manually test migration of other devices to an actual
+  # wpad-mesh-wolfssl (or similar) variant.
+  package_wpad_full: &package_wpad_full
+    - name: wpad-basic-wolfssl
+      state: absent
+    - name: wpad-mesh-wolfssl
+      state: absent
+    - name: wpad-wolfssl
+      state: present
+
 openwrt:
   hosts:
     ap3825i1.lan: