Add nudge unit

[freezy]

This PR adds a Nudge Visual Scripting unit for table logic.

• Adds a new Pinball > Nudge unit.
• Exposes Angle and Force inputs.
• Calls Player.Nudge(angle, force) and continues graph flow through the output trigger.

This lets Visual Scripting tables trigger the same player nudge path used by the engine-side nudge implementation.

[greptile-apps]

Greptile Summary

This PR adds a Visual Scripting node for triggering player nudges. The main changes are:

• New Pinball > Nudge unit under Runtime/Nodes/Nudge.
• Angle and Force value inputs with control-flow ports.
• Runtime call from the node to Player.Nudge(angle, force).
• Unity metadata for the new folder and script.

Confidence Score: 4/5

The new node depends on the resolved engine package exposing the exact Player.Nudge API.

• The node structure matches existing Visual Scripting unit patterns.
• The compile path can break if the referenced Player type does not provide a compatible two-float Nudge method.
• No security issue was identified in the changed code.

Runtime/Nodes/Nudge/NudgeUnit.cs

Important Files Changed

Filename	Overview
Runtime/Nodes/Nudge/NudgeUnit.cs	Adds the new NudgeUnit node and wires it to the external Player.Nudge API.
Runtime/Nodes/Nudge.meta	Adds standard Unity folder metadata for the new node directory.
Runtime/Nodes/Nudge/NudgeUnit.cs.meta	Adds standard Unity script metadata for the new node class.

_{Reviews (1): Last reviewed commit: "visualscripting: add nudge unit" | Re-trigger Greptile}

[greptile-apps]

External Nudge API Coupling

Player is provided by the referenced VisualPinball.Unity assembly, so this new call requires that package version to expose a compatible public Nudge(float, float) overload. If the resolved engine package lacks that exact API or uses a different signature, the Visual Scripting runtime assembly will fail to compile when this node is added.