Node settings arrive as keyword arguments, not a params dict

A python node's settings are constants of its own function, so they are passed
the way its ports are: by name. The controller binds them to the compiled
function, the `params` field is gone from the worker and remote protocols, and
a setting sharing a port's name is reported as a node error rather than
shadowing it. The panel's scaffold follows suit and keeps the header in step
with both ports and settings.

The demo's `pace` moves from a flow input to a setting of the training node,
which is what it always was.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NUb8YpL2s3gmN9WTACTt4q

frontend/tests/runtime.spec.ts

@@ -12,11 +12,11 @@ test.use({ storageState: "playwright/.auth/user.json" })
 
 test.describe.configure({ mode: "serial" })
 
-const PRINTING_NODE = `def process(params):
+const PRINTING_NODE = `def process():
     print("sensor read 21.5 degrees")
     return {"reading": 21.5}
 `
-const BROKEN_NODE = `def process(reading, params):
+const BROKEN_NODE = `def process(reading):
     raise RuntimeError("downstream blew up")
 `