Tabular extension exec tests

[f3l1x98]

Closes #417

This PR adds tests to all the block-executors of the tabular extension.

Note: This conflicts with #456 (this is newer -> the other will have to be adjusted)

Important changes

• Moved the file-util.ts from libs/extensions/std to libs/execution due to required usage in tabular extension tests.
• Extracted libs/extensions/std/exec/src/text-file-interpreter-executor.ts#splitLines into lib/execution/src/lib/util/string-util.ts also due to usage in tabular tests
• Refactored libs/execution/test/utils.ts into folder with multiple utils (old utils.ts renamed to utils/test-infrastructure-util.ts)
• Added jsdom fixes for structuredClone and setImmediate

[f3l1x98]

I have found two things that need clarification:

1. jayvee/libs/extensions/tabular/exec/src/lib/table-interpreter-executor.ts

   Lines 232 to 234 in 2240655

   	const indexOfMatchingHeader = headerRow.findIndex(
   	(headerColumnName) => headerColumnName === columnDefinition.name,
   	);

   
   Is this case-sensitive on purpose?
2. If the TableInterpreterExecutor is called for a Sheet with data (for example 8 rows of data) but with columnDefinitions: []; this will result into a table that satisfies the following:

      // [...]
      const result = await parseAndExecuteExecutor(
        text,
        testWorkbook.getSheetByName('Sheet1') as R.Sheet,
      );
      // [...]
      const table = result.right;
      expect(table.getNumberOfColumns()).toEqual(0);
      expect(table.getNumberOfRows()).toEqual(8);

This is due to Table#addRow only verifying whether rowLength === this.columns.size, however that is always true in this case because TableInterpreterExecutor#constructAndValidateTableRow returns an empty TableRow if there are no columns. Due to that Table#addRow will be executed without any issue and increment the row count, however there is no data in the table.
TLDR: Table indicates there are rows stored, even though there are none (there should not be any).

[georg-schwarz]

1. jayvee/libs/extensions/tabular/exec/src/lib/table-interpreter-executor.ts

   Lines 232 to 234 in 2240655

   	const indexOfMatchingHeader = headerRow.findIndex(
   	(headerColumnName) => headerColumnName === columnDefinition.name,
   	);

   Is this case-sensitive on purpose?

Yes, I believe so.

2. If the TableInterpreterExecutor is called for a Sheet with data (for example 8 rows of data) but with columnDefinitions: []; this will result into a table that satisfies the following:

      // [...]
      const result = await parseAndExecuteExecutor(
        text,
        testWorkbook.getSheetByName('Sheet1') as R.Sheet,
      );
      // [...]
      const table = result.right;
      expect(table.getNumberOfColumns()).toEqual(0);
      expect(table.getNumberOfRows()).toEqual(8);

This is due to Table#addRow only verifying whether rowLength === this.columns.size, however that is always true in this case because TableInterpreterExecutor#constructAndValidateTableRow returns an empty TableRow if there are no columns. Due to that Table#addRow will be executed without any issue and increment the row count, however there is no data in the table. TLDR: Table indicates there are rows stored, even though there are none (there should not be any).

Good catch! I'd expect that only a row is added if there is data in it.
It might only make sense when you add all empty rows, then add content to the rows by adding columns. But I don't think we use this anywhere.

[f3l1x98]

Good catch! I'd expect that only a row is added if there is data in it.
It might only make sense when you add all empty rows, then add content to the rows by adding columns. But I don't think we use this anywhere.

We decided that this fix is ok, we just have to document this behavior somewhere.