chore(core): improve typing of Runnable __or__

[cbornet]

No description provided.

[codspeed-hq]

CodSpeed Performance Report

Merging #34530 will not alter performance

_{Comparing cbornet:improve-runnable-or (d51225b) with master (e03d6b8)¹}

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

✅ 13 untouched
⏩ 21 skipped²

Footnotes

1. No successful run was found on master (721bf15) during the generation of this report, so e03d6b8 was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 21 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[cbornet]

I guess we are doing that on purpose

[cbornet]

This is needed for instance when chain = input_map | router (see test_higher_order_lambda_runnable)

and

def router(params: dict[str, Any]) -> Runnable[dict[str, Any], str]:

[cbornet]

I think mypy is right: RunnablePick needs a dict[str, Any] as input so it cannot be piped to any Runnable.
Shouldn't it be implemented only for specific subclasses ?