Duplicated versions of jecs do not emit useful error messages

[kurokuukyo]

Describe the bug

When using jecs and the user unintentionally has multiple versions of jecs in use, the NULL_ARRAY variable can be used across versions, causing error messages because jecs only checks for its own local copy. I believe this should be the default behavior, but it can use more useful error messages.

Reproduction

This issue happens whenever two versions of jecs operate on a query. The easiest example I can think of to demonstrate this is how the jecs-utils project uses a local copy of jecs to act on queries. If these versions mismatch, the bug occurs.

What makes this bug tricky to debug is that the code at issue doesn't immediately trigger the bug, a subsequent add/set/remove operation causes the error because it can't write to the columns.

For note, I believe this covers every attempt to modify a readonly table error in the codebase.

Expected Behavior

Jecs should catch this error in debug mode and emit a message saying not to use multiple versions of jecs.

Actual Behavior

Error messages that are not useful for debugging this issue

[kurokuukyo]

that's sad

This is a bug where the root cause hasn't really been talked about. If you've been paying attention on the ROSS server where the project thread is hosted, you can find multiple people complaining about this bug with no real insight as to why it happens. This issue is just meant to track it and propose that more useful error messages are emitted than what is currently present.