Strategy to forward prefix parameter when creating blocks

[glemaitre]

After a couple of hours looking at the code, I thought that it might be possible to keep track of the parameter prefixes (e.g. pipeline__ridge__***) during the recursive call to _write_estimator_html. To be honest, I got help from an Claude to do so :)

So we should extensively test it and look at the diff to know if it the right way to go.

But at least the changes look OK for the moment. I will check if works with string, meta-estimator and column transformer.

[github-actions]

❌ Linting issues

This PR is introducing linting issues. Here's a summary of the issues. Note that you can avoid having linting issues by enabling pre-commit hooks. Instructions to enable them can be found here.

You can see the details of the linting issues under the lint job here

---

ruff

ruff detected issues. Please run ruff check --fix --output-format=full . locally, fix the remaining issues, and push the changes. Here you can see the detected issues. Note that the installed ruff version is ruff=0.5.1.

sklearn/utils/_get_params_html_repr.py:87:89: E501 Line too long (99 > 88)
   |
85 |                 // Get the parameter prefix from the closest toggleable content
86 |                 const toggleableContent = element.closest('.sk-toggleable__content');
87 |                 const paramPrefix = toggleableContent ? toggleableContent.dataset.paramPrefix : '';
   |                                                                                         ^^^^^^^^^^^ E501
88 |                 const fullParamName = paramPrefix ? `${paramPrefix}${text}` : text;
   |

Found 1 error.

_{Generated for commit: 430f6a0. Link to the linter CI: here}