Update theme/style sheet handling to enable napari-console to use napari font_size setting

[dalthviz]

References and relevant issues

Closes #32

Description

Depends on/related to napari/napari#6753

A preview:

Notes

• While working on this, I noticed that with napari latest main a deprecation warning appears (related with using the as_dict kwarg from the get_theme function). Added a note about that here.
• To preserve compatibility with napari 0.4.x (at least 0.4.19) the previous logic was left. The new style_sheet kwarg added to the _update_theme method defines if the previous logic needs to be used (napari 0.5.0 will use the new style_sheet kwarg, see Use font_size setting to control napari-console font-size napari#6753)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.77%. Comparing base (e2a8d71) to head (0b219dd).

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #33      +/-   ##
==========================================
+ Coverage   96.69%   96.77%   +0.07%     
==========================================
  Files           4        4              
  Lines         121      124       +3     
==========================================
+ Hits          117      120       +3     
  Misses          4        4              

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

[Czaki]

This is not correct approach. You either need to disconnect _update_theme from self.viewer.events.theme event or update _update_theme to read font size from settings

[jni]

@Czaki does @dalthviz's latest commit address your concerns?

[Czaki]

I just installed this PR and I do not see any changes when update theme or font size.

I do not see connection to any proper signal in the code

[dalthviz]

Did you check this alongside napari/napari#6753 @Czaki ? I checked again and works for me on Windows 🤔 (although as mentioned I see a deprecation warning related with the as_dict kwarg):

Anyhow, maybe the work over napari/napari#6753 and here is not the correct approach and these PRs should be closed?

[DragaDoncila]

@Czaki do you want to have another look at this after Daniel's last comment? Should this PR be closed or is it the right approach?