Implemented Data Editor Message Registry

[stricklandrbls]

Closes #1659
Closes #1469
Closes #1058
Closes #669

Description

• Implemented a Message Registry which provides type-safe message content inspection for messages sent between the data editor, dfdl extension, and the Svelte UI.
• Restructured some legacy Svelte stores into Svelte v5 runes.
• Resolved issues related to message content mismathcing and message content being processed by multiple data editors when the message was intended for a single data editor instance.

Wiki

• I have determined that no documentation updates are needed for these changes
• I have added the following documentation for these changes

Review Instructions including Screenshots

Developer Perspective Reviews

1. In any portion of the data editor's extension source, verify that message content is appropriately inspected and the VSCode intellisense engine emits correct types when invoking this.panel.postMessage(...).

Screenshots ( dataEditorClient.ts -> 'fileInfo')

2. In any portion of the data editor's Svelte UI source, verify that message content is appropriately inspected and the VSCode intellisense engine emits correct types when invoking addListener(...).

Screenshots ( DataEditorLineFeed.svelte -> 'viewportRefresh')

3. In any portion of the data editor's Svelte UI source, verify that message content is appropriately inspected and the VSCode intellisense engine emits correct types when invoking vscode.postMessage(...).

Screenshots ( App.svelte -> 'requestEditedData')

---

Functionality Review

Verify that all message traffic behaves as expected. Message content can be identified within the ./src/ext_types/message.ts & ./src/ext_types/messageContent.ts

[stricklandrbls]

Looks like I'll have to fix tests due to the strict type checks when transpiling with yarn tsc

[stricklandrbls]

@scholarsmate Is the omegaEditServerLifecycle.ts a test file? The CI jobs are failing due to a permission denied when trying to run the transpiled JS file.

Disregard, I fixed this issue.

[stricklandrbls]

Some changes needed to be made in order to get the updated data editor files to function properly for CI. Everything should be good to go, now.

[hdalsania]

@stricklandrbls Is this PR ready to test?

[stricklandrbls]

@stricklandrbls Is this PR ready to test?

Yes it is ready

[stricklandrbls]

Going to sift through and implement resolutions for import strings as referenced here

[stricklandrbls]

The svelte imports should now all be aliased if the path is not a sub-directory of its path.

The rest of the extension imports still need to be updated.

[lrbarber]

@stricklandrbls , I did some testing on this code and found that the data editor does not open automatically when starting debug. Wondering if some messages are missing? The status bar at the bottom shows no indication that it is even trying to connect to the server.
Opening the data editor manually works, but it does not get the location tracking indicator. Also, after closing the editor and restarting debug, attempting to open data editor again results in an error: A Data Editor already exists for .

[stricklandrbls]

@stricklandrbls , I did some testing on this code and found that the data editor does not open automatically when starting debug. Wondering if some messages are missing? The status bar at the bottom shows no indication that it is even trying to connect to the server.

Opening the data editor manually works, but it does not get the location tracking indicator. Also, after closing the editor and restarting debug, attempting to open data editor again results in an error: A Data Editor already exists for .

Awesome thanks for testing this. I'll take a look

[stricklandrbls]

@lrbarber The latest commit should fix the issue of the Data Editor not opening for the target data file in a debug session.