Clarifications on "more complex" unchanged instructions

We should clarify if the following specifications are desired:

• table.copy can copy between shared and unshared tables (all 4 combinations[^1], also for all the other cases below)
• array.copy can copy between shared and unshared arrays
• table.init can initialize shared and unshared tables from shared and unshared element segments
• array.new_elem can construct shared and unshared arrays using shared and unshared element segments
• array.new_data can construct shared and unshared arrays using shared and unshared data segments
• array.init_data and array.init_elem can similarly use a mix of shared and unshared arrays and element / data segments

AFAICT that's what this proposal is currently defining, I can say for sure that the V8 implementation does not support most of these cases (some of the bulk instructions might not work at all for shared types in the current POC.)

[^1]: Inside an unshared function

Start by reading the proposal's treatment of "more complex" unchanged instructions and compare the listed shared/unshared combinations with the V8 proof-of-concept implementation. Done means the proposal explicitly resolves whether each table, array, element-segment, and data-segment combination is supported.