Fix the CJS recipes entry eagerly loading nested d3-geo

Problem

A published CJS consumer importing a non-geo layout from semiotic/recipes can fail in Jest with SyntaxError: Unexpected token 'export' from d3-geo.

Two defects compound:

1. The CJS recipes bundle is monolithic and eagerly requires d3-geo even for non-geo recipes.
2. The declared d3-geo@^3.1.1 floor can force a nested install beside the common d3 meta-package dependency on 3.1.0, escaping consumer transform allowlists.

The public geographicDotGridLayout export must remain available from semiotic/recipes; removing or moving it is not a compatible fix.

Acceptance criteria

• Loading a non-geo recipe through the built CJS recipes entry does not load d3-geo.
• An external-consumer packaging test resolves the require condition against dist/.
• Every non-geo public entry is checked for reachable d3-geo.
• The minimum required d3-geo version is documented from APIs actually called; widen the range if justified.
• A fresh workspace that also installs the d3 meta-package has no unnecessary nested d3-geo.
• Public recipe exports and package/API checks remain unchanged.

Roadmap source: Packaging defect EXP-27472.

Start at the built CJS recipes entry and its dist/ output, then locate the external-consumer packaging test that resolves the require condition. Trace which non-geo public entries can reach d3-geo and inspect the APIs used to determine the supported version range. Done means non-geo loads avoid d3-geo, packaging and API checks pass, and public exports remain unchanged.