Let Get position give only the local x and y

Get world position now covers the world coordinates. Two nodes that
both offer world x and y made it unclear which one to take. No project
uses the world outputs of Get position any more.

- Get position drops its world x and world y outputs and its
  description points to Get world position.
- Old snapshots with edges on those outputs still load. The edges hang
  on ghost ports and the node warns about them.
- The unit tests in hierarchy and raycast and the graphs in e2e 43 use
  Get world position where they read the world coordinates.

Tests:
- node-catalog, hierarchy, raycast: 3 files, 417 tests, all green
- e2e 43 on melektaus-atx: ALL PASSED, 17 checks

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

tests/core/node-catalog.test.ts

@@ -737,20 +737,16 @@ const CASES: Record<string, Case[]> = {
   ],
   GetPosition: [
     {
-      name: 'local and world position of a top-level object are the same',
+      name: 'a top-level object is at its own position',
       inputs: { object: at('A', 10, 20) },
-      outputs: { x: 10, y: 20, worldX: 10, worldY: 20 },
+      outputs: { x: 10, y: 20 },
     },
     {
-      name: 'a child reports its local position and the summed world position',
+      name: 'a child reports its position local to the parent',
       inputs: { object: { ...at('child', 10, 20), parent: at('parent', 100, 200) } },
-      outputs: { x: 10, y: 20, worldX: 110, worldY: 220 },
-    },
-    {
-      name: 'no object is the origin',
-      inputs: { object: null },
-      outputs: { x: 0, y: 0, worldX: 0, worldY: 0 },
+      outputs: { x: 10, y: 20 },
     },
+    { name: 'no object is the origin', inputs: { object: null }, outputs: { x: 0, y: 0 } },
   ],
   GetWorldPosition: [
     {