Schematic to solid model rendering does not honor strict for geometry failures

`render!(::SolidModel, ::Schematic, ::SolidModelTarget; strict=...)` lets component geometry exceptions escape. They are not logged, so `strict=:no` cannot replace failed geometry with empty geometry and continue, as documented in the docstring.

MRE:

```julia
using DeviceLayout
using DeviceLayout.SchematicDrivenLayout
using DeviceLayout.SolidModels
import DeviceLayout.SchematicDrivenLayout: _geometry!

@compdef struct BrokenComponent <: Component
name::String = "broken"
end

function SchematicDrivenLayout._geometry!(::CoordinateSystem, ::BrokenComponent)
error("intentional geometry failure")
end

graph = SchematicGraph("broken")
add_node!(graph, BrokenComponent())
schematic = plan(graph; log_dir=nothing) |> check!
target = SolidModelTarget(ProcessTechnology((;), (;)))
model = SolidModel("broken"; overwrite=true)

render!(model, schematic, target; strict=:no)
```

**Expected:** rendering continues with empty geometry for the failed component.

**Actual:** `ErrorException: intentional geometry failure` escapes, and the `:render_solidmodel` log level remains `Debug`. `strict=:error` produces the same raw exception rather than a logger-based strictness error.

Start at the `render!(::SolidModel, ::Schematic, ::SolidModelTarget; strict=...)` implementation and its docstring, then reproduce the supplied `BrokenComponent` MRE. Trace how `_geometry!` exceptions and the `:render_solidmodel` log level are handled for `strict=:no` and `strict=:error`. Done means failed geometry is replaced with empty geometry in non-strict mode, while strict mode reports the failure through the logger.

Written by the indexing model from the issue text.