FIREFLY-2066: Consolidate the loading UI of Spectral Lines feature

[jaladh-singhal]

Fixes FIREFLY-2066

• Moved the spectral lines panel out of Chart options into its own dialog (toolbar button, left side) rendering SpectralLinesPanel - loading is a separate concern from per-trace display options, and the panel is shared app-wide, not per-chart
• Recommended line lists are now driven by a charts.spectrum.linelists app-config property ({label, src?} array, src can be a bundled resource or remote URL) instead of one hardcoded combined CSV - retired linelist_combined.csv for separate hspot_lines.csv/pahfit_lines.csv/spherex_lines.tbl resources plus a remote JWST list as a src-as-URL example
• Checked lists and the uploaded list merge into one client-side table (spectral-lines), rebuilt only on explicit "Load Lines"/"Clear All", never automatically on checkbox/mapping change
• Wavelength units normalize to microns at merge time for both sources; SpectralLinesProcessor warns server-side when an available line list's wavelength column has no units metadata, and the upload column mapper shows similar feedback for the uploaded file's wavelength column

Additional changes/cleanup:

• UploadTableSelector enhanced for use in SpectralLinesPanel: added allowClear (adds a chip to clear the uploaded file), uploadTblOptions (keeps the upload out of the main Results view), and a per-field getFeedback hook (surfaces the uploaded wavelength column's detected/assumed unit)
• SpectrumOptions: Standardized default resolution logic for redshift options (getEffectiveSpectralFrameOption) and de-duplicated a few hardcoded spectral-frame/redshift constants
• Added µJy as a supported flux unit in SpectrumUnitConversion (for SPHEREx spectrum results)
• Fixed an off-center "no data" message in BasicTableView

Testing

All the test files linked in the ticket.

https://firefly-2066-spec-lines-loading.irsakubedev.ipac.caltech.edu/firefly

Core functionality

1. Upload "60..." (SPHEREx spectrum) -> open the spectral lines dialog from the top-left of the "Active chart" tab -> select the SPHEREx line list -> "Load Lines". They should populate the Lines table in the dialog and get plotted in the chart
2. Deselect a couple of lines from the table - they should disappear from the chart in real time. Filter the lines table by label "Paschen" -> only Paschen lines should show up. Close the dialog
3. Now upload the "Spitzer_IRS..." spectrum. The spectrum chart should plot with the same line selection as the previous spectrum
4. Open the spectral lines dialog for this (2nd) spectrum, make changes to the line selection here -> switch back to the 1st spectrum's table tab -> the spectral lines in the 1st spectrum's active chart should have updated compared to before
5. "Clear All" in the dialog should remove all lines from all charts - a one-click revert to the app's initial state

Upload line list

• Upload "jwst_linelist.tbl" in the "Select line lists to load" collapsible -> map columns, confirm feedback text and loading behavior
• The "Clear" chip should remove the uploaded list - the same behavior as unchecking an available-list checkbox

Redshift correction

• Open "Chart options" for an active spectrum with "Observed Frame" selected -> under "Redshift correction," set "Enter Redshift" to 0.5 and "Apply" -> spectral lines should redshift right of their lines-table wavelength. Switch to "Rest Frame" with the same redshift and "Apply" -> lines return to their original wavelength and the spectrum blueshifts left instead. Net effect: lines and spectrum end up in the same relative position, just with the X-axis shifted - confirming the correction applies correctly in both frames
• Most of our spectrum files have no "target"/"derived" redshift in their metadata, so they start at zero redshift correction - "Spitzer_IRS..." is the exception. Refresh the app, load it, and in the spectral lines dialog load the SPHEREx line list -> lines should plot correctly shifted (the last line's wavelength in the Lines table should be less than its hover-tip wavelength in the chart). Open "Chart options" -> "Observed Frame" and the target redshift should already be selected, confirming this is the factor lines were shifted by. This verifies the redshift is picked up correctly even when Chart options was never opened (so it's not yet in the chart store)

Regression

• Pinned charts should propagate spectral lines and otherwise work as before
• Upload two "table_OBJECT.." (Euclid) spectrum files -> pin their charts -> in "Pinned Charts," combine them using the toolbar's combine option (two-rings icon) -> spectral lines should propagate without affecting the combine functionality
• Grouped traces should work as before

[jaladh-singhal]

NOTE: Last option "JWST line list (remote)" is just a test for recommended/pre-installed line list coming from a remote server rather than bundling with firefly static resources.

I plan to remove it when merging this PR.

[lrebull]

This is so cool!

See here for two items, at least on my screen:

Item 1: The labels are a tiny bit too far away from their line. I've weeded down this list, but even so, on the edges you can see that the label for "OCS" is actually closer to the line for "13 CO" than it is its own line, and same for Paschen gamma -- it's closer to Paschen delta than its own line. These need to be a bit closer to the corresponding line, IMHO.

Item 2: you can see here how a lot of the labels run off the top. Less than ideal. Is there a way for users to tweak this? move them down?

I love the dynamic response of the pop-up. At the end of the process, we have this at the bottom of the pop-up:

We have trained people elsewhere that clicking on the green version of that little plot icon does things. Now it's blue, and clicking on it doesn't do anything. Is that good UI/UX? The arrow at the end also doesn't do anything. What is it meant to indicate? I mean, the first thing I did with the pop-up was grab and move it to cover the image in the tri-view so that i could see the plot, and maybe that makes me different than you expected?

Ooh, this should not be default behavior:

even if the line list goes out past 50 um, if the data only go to 8.6 um, the plot, even after adding the line list, should only go to 8.6 um. The priority should be to show me the data, not the line list.

Actually, this is a problem. Look, I've tried to weed the line list down to only be <8.6 um, and the table is filtered appropriately (see scrollbar on the line list), but the plot is showing me lines >8 um.

OH WAIT you applied a redshift to FV Tau/c ?!? lolololol ok you threw me for a loop with that one. This thing is 140 pc away; it definitely doesn't have a redshift of 0.546. But the plot says "observed frame" not "rest frame" ... hm. I'm still confused; we need an xgal person to look at this.

In any case, I think what we need to do is echo the redshift to the top of the spectral line list. In between the "select line lists to load" pulldown thing, and before "select lines to plot", I propose something in italics: "redshift has been applied to lines in plot; see plot options" or something better than that. (i'm sure others will Have Opinions.) The idea is to get a pointer or hint or something in here, because I, for one, didn't understand what could possibly be going on here.

Let me see if I can get some other scientists in on this.