fix: support pl.UInt type in nanoplot

[jrycw]

Fix: #571

It seems the issue stems from the input being a type we didn’t anticipate. While more advanced types like pl.Enum, pl.Categorical, pl.Array, pl.List or pl.Struct could introduce additional complexity, this PR addresses the simpler part for now.

Since _str_detect() is clearly an internal function, we could consider modifying it. However, if we switch to using re.search(), the following test cases will fail:

- FAILED `tests/test_formats.py::test_fmt_nanoplot_polars_listcol` - assert [- snapshot] == [+ received]  
- FAILED `tests/test_utils_render_html.py::test_render_polars_list_col` - assert [- snapshot] == [+ received]  

If we opt not to modify _str_detect(), we need to handle uint as a numerical type, as implemented in this PR.

Additionally, I noticed that the alignment of pl.UInt might require adjustment.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.67%. Comparing base (9366829) to head (d7be45c).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #577   +/-   ##
=======================================
  Coverage   90.67%   90.67%           
=======================================
  Files          46       46           
  Lines        5381     5381           
=======================================
  Hits         4879     4879           
  Misses        502      502           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.