build: Move test applications and the defaultapp

Instead of having the test apps under fw we create a new directory for
them.

hw/application_fpga/apps/README.md

@@ -0,0 +1,18 @@
+# Test applications
+
+All of these test apps are controlled through the USB CDC, typically
+by running picocom or similar terminal program, like:
+
+```
+$ picocom /dev/ttyACM1
+```
+
+- `defaultapp`: Immediately resets the TKey with the intention to
+  start an app from the client, replicating the behaviour of earlier
+  generations.
+- `testapp`: Runs through a couple of tests that are now impossible
+  to do in the `testfw`.
+- `reset_test`: Interactively test different reset scenarios.
+- `testloadapp`: Interactively test management app things like
+  installing an app (hardcoded for a small happy blinking app, see
+  `blink.h` for the entire binary!) and to test verified boot.

hw/application_fpga/fw/README.md

@@ -812,22 +812,5 @@ ordinary `application_fpga/Makefile` to be able to fit in ROM.
 
 ### Test apps
 
-There are a couple of test apps. All of them are controlled through
-the USB CDC, typically by running picocom or similar terminal program,
-like:
+There are a couple of test apps, see `../apps`.
 
-```
-$ picocom /dev/ttyACM1
-```
-
-or similar.
-
-- `fw/defaultapp`: Immediately resets the TKey with the intention to
-  start an app from the client, replicating the behaviour of earlier
-  generations.
-- `fw/testapp`: Runs through a couple of tests that are now impossible
-  to do in the `testfw`.
-- `fw/reset_test`: Interactively test different reset scenarios.
-- `fw/testloadapp`: Interactively test management app things like
-  installing an app (hardcoded for a small happy blinking app, see
-  `blink.h` for the entire binary!) and to test verified boot.