Fix silkscreen paths causing extra pins in schematic view

Related to tscircuit#308

Add method to prevent silkscreen paths from being interpreted as pins in schematic view.

* **SilkscreenPath.ts**
  - Add `doInitialSchematicComponentRender` method to `SilkscreenPath` class to prevent silkscreen paths from being interpreted as pins in the schematic view.
* **silkscreenpath.test.tsx**
  - Add test case to verify that silkscreen paths are not interpreted as pins in the schematic view.

lib/components/primitive-components/SilkscreenPath.ts

@@ -46,4 +46,8 @@ export class SilkscreenPath extends PrimitiveComponent<
 
     this.pcb_silkscreen_path_id = pcb_silkscreen_path.pcb_silkscreen_path_id
   }
+
+  doInitialSchematicComponentRender(): void {
+    // This method intentionally left blank to prevent silkscreen paths from being interpreted as pins in the schematic view
+  }
 }

tests/components/primitive-components/silkscreenpath.test.tsx

@@ -36,3 +36,27 @@ test("SilkscreenPath rendering", () => {
 
   expect(project).toMatchPcbSnapshot(import.meta.path)
 })
+
+test("SilkscreenPath not interpreted as pins in schematic view", () => {
+  const { project } = getTestFixture()
+
+  project.add(
+    <board width="10mm" height="10mm">
+      <silkscreenpath
+        route={[
+          { x: "0mm", y: "0mm" },
+          { x: "5mm", y: "5mm" },
+          { x: "10mm", y: "0mm" },
+        ]}
+        strokeWidth="0.2mm"
+        layer="top"
+      />
+    </board>,
+  )
+
+  project.render()
+
+  const schematicPins = project.db.schematic_pin.list()
+
+  expect(schematicPins.length).toBe(0)
+})