ISSUE-648: Change status classes to functional components

[ada333]

#648
This PR refactors these classes into functional components:

1. CellMetadataEditor
2. InlineCellsMetadata
3. InlineMetadata
4. StatusRunning
5. StatusTerminated

For better code quality and readability there were some new hooks and separate component files added:
New hooks:

1. useUpdateCellTags -- encapsulates all Kale cell metadata write operations
2. useEditorPosition -- manages editor DOM positioning inside the active notebook cell
3. useInlineCellsMetadata -- manages inline metadata portals, editor props, and active cell tracking
4. useNotebookSignals -- connects/disconnects JupyterLab notebook signals (save, cell change, active cell, metadata)
5. useLatestRef -- utility hook to avoid stale closures in signal handlers

New dialog components (extracted from CellMetadataEditor):

1. BaseImageDialog
2. CacheDialog
3. GpuDialog (renamed from CellMetadataEditorDialog)

Other cleanup:

1. Shared constants moved to constants.ts
2. Dialog components organized into dialogs/ folder
3. Removed dead commented-out code

Left Panel will be refactored in another PR.

TESTING:

To test this I spinned up jupyter lab with these changes and jupyter lab from main and I compared the behaviour of UI. I recommend for testing of this PR to do the same thing.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ederign for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jesuino]

Hello Adam,

Thanks for your work on this, I checked the other PR and it is looking good! Would it be possible to do all work in a single PR? It will even better for your to work on a single PR because when you get to dependent components you may have weird behavior related to state mismatch.

Thanks!

[jesuino]

Can we take this opportunity to remove unused comments?