test(fls): the Java oracle opens files as FILIUS does (M8)

FlsOracle now loads through SzenarioVerwaltung.laden, FILIUS's full
loading path: the archive unpacked, the project's own applications copied
where FILIUS's class loader finds them, then the configuration.
--network keeps the configuration-only load (netzwerkLaden).

On the corpus this changes two files: anwendung_komplett.fls and
multicast_server.fls then have their own applications (Accumulator,
Broadcast) installed. Java's views of the written and the exported files
are byte-equal to before: Java-FILIUS 2.14 opens our exports, with the
classes they carry, as it opens a file of its own, and sees what it sees
in the original. Until own applications on hosts are written (B2), the
reader, writer and export tests leave them out (test/ownApplications.ts);
a test checks that only those two files are touched.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

corpus/corpus.java.json

@@ -8021,7 +8021,14 @@
             "directory": "root",
             "children": []
           },
-          "applications": [],
+          "applications": [
+            {
+              "key": "filius.software.clientserver.Accumulator",
+              "class": "filius.software.clientserver.Accumulator",
+              "aktiv": true,
+              "port": 55555
+            }
+          ],
           "dhcpClient": false,
           "dhcpServer": {
             "aktiv": false,
@@ -13239,6 +13246,12 @@
             "children": []
           },
           "applications": [
+            {
+              "key": "filius.software.clientserver.Broadcast",
+              "class": "filius.software.clientserver.Broadcast",
+              "aktiv": true,
+              "port": 55555
+            },
             {
               "key": "filius.software.clientserver.ServerBaustein",
               "class": "filius.software.clientserver.ServerBaustein",