Replace the AssetCompareDialog, VisibilitySelector and Logs dropdowns

[cstns]

Description

Replace the AssetCompareDialog, VisibilitySelector and Logs dropdowns

Related Issue(s)

close #4562

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• Includes a DB migration? -> add the area:migration label

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.30%. Comparing base (a1cc1c5) to head (00197f4).
Report is 23 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4580   +/-   ##
=======================================
  Coverage   78.30%   78.30%           
=======================================
  Files         302      302           
  Lines       14360    14360           
  Branches     3265     3265           
=======================================
  Hits        11244    11244           
  Misses       3116     3116           

Flag	Coverage Δ
backend	78.30% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[Steve-Mcl]

Nice that we can now type to get to item and esc to close etc. however there are 2 small issues:

1. The size of the dropdown does not have a min width AND/OR doesnt compute a min width from entries and so collapses to an unreadable narrow list when a short item is selected

selection 1 - it expands

selection 2 - it collapses

2. The snapshot compare list contains empty rows

[Steve-Mcl]

@cstns
Functionally, I am now happy with this.

Code wise also good however I am curious about the CSS. In particular, the affect or potential impact of using such common class names like "option", "options" and "button" in the controls. Prior to this work, they were much less likely to be impacted by any stray CSS classes as they were more verbose e.g ff-dropdown-options.

Feel free to tell me this is nothing to worry about and proceed.

issue with dialog css

[Steve-Mcl]

Dismissed review until dialog header CSS fix is pushed

[cstns]

fix incoming, pending tests running locally