Perform a dry run of the preprocessor when initializing a sync

[WolfGangS]

This triggers a run of the preproc on a sync being established, populating the included file list so that if any one of them is saved the script is processed and sent to sl.

[Rider-Linden]

I don't think this is required. You should be able to pull any required files from the scriptSync.lineMappings member.

On initial subscription the plugin scans the file and generates an initial line mapping by looking for @line directives in the source.

See:
https://github.com/secondlife/sl-vscode-plugin/blob/develop/src/scriptsync.ts#L111-L119

and:
https://github.com/secondlife/sl-vscode-plugin/blob/develop/src/shared/linemapper.ts#L20-L65

[WolfGangS]

That wont work, as the scripts on disk may have changed since the last time the one in world was edited.

We do not want what the script from SL "thinks" might be the relevant files. But the files on disk that the matched workspace script depends on.

Imagine you have updated a dependency, then go to save that again, and wonder why the script you just loaded hasn't re-saved in sl, because that wasn't included last time.