Kuahchou/2396 new RESTFQ for moment

[loveluthien]

Description

This closed #2396 together with backend PR and its companion protobuf. This PR adds the rest frequency GUI to the moment generator.

Checklist

For linked issues (if there are):

• assignee and label added
• GitHub Project estimate added

For the pull request:

• reviewers and assignee added
• GitHub Project estimate added
• changelog updated / no changelog update needed
• unit test added (for functions with no dependenies)
• API documentation added (for public variables and methods in stores)

For dependencies:

• e2e test passing / corresponding fix added / new e2e test created
• protobuf version bumped / no protobuf version bumped needed
• protobuf updated to the latest dev commit / no protobuf update needed
• corresponding ICD test fix added (BackendService changed) / no ICD test fix needed (BackendService unchanged)
• user manual prepared (for large new features)

[kswang1029]

Regarding changing the unit of rest frequency definition, there are possible use cases:

1. user manually types in the value: in this case, user needs to configure the right unit first before typing. Or user needs to convert the value in mind if the selected unit is different from the one in user's mind (mostly the value is read from a catalog)
2. user copies and pasts a value from a catalog: in this case, users need to configure the right unit first before pasting. If pasting happens first and changing the unit later, the value will be changed too.

In both cases. the new feature (synchronize the value and unit) does not help the UX and sometimes hurts. I suggest we keep the original way (desynchronize the value and unit)

[loveluthien]

Regarding changing the unit of rest frequency definition, there are possible use cases:

1. user manually types in the value: in this case, user needs to configure the right unit first before typing. Or user needs to convert the value in mind if the selected unit is different from the one in user's mind (mostly the value is read from a catalog)
2. user copies and pasts a value from a catalog: in this case, users need to configure the right unit first before pasting. If pasting happens first and changing the unit later, the value will be changed too.

In both cases. the new feature (synchronize the value and unit) does not help the UX and sometimes hurts. I suggest we keep the original way (desynchronize the value and unit)

Okay.

[kswang1029]

When there is no image loaded, if we enable the spectral profiler widget and then enable its settings dialog, the frontend will crash.

[loveluthien]

update:

• Fix the frontend crash when no image loaded.
• disable the rest freq. function in the moment generator following SpectralSettingsComponent.

[kswang1029]

looks nice. 👍 added new e2e tests

[YuHsuan-Hwang]

The implemented UI looks good. Just some minor comments:

[YuHsuan-Hwang]

Pending for CARTAvis/carta-backend#1387 code review.