New API for supporting mut aliasing safety

[Indra-db]

This PR introduces:

• locking for either component records (sparse components) or table-column locks (non-sparse components).
• separate per-thread / per-stage locking for table columns.
• everything gated by the FLECS_MUT_ALIAS_LOCKS define, so there is no performance impact when it’s not enabled.
• build tests and unit tests for the behaviour.

End users of this internal API must use it themselves and panic when the mut-alias guarantee is violated.

ecs_lock_target_t holds information about where the lock should be applied. For sparse components/IDs (sparse and/or non-fragmenting) it will use the component_record for locking. For table-column components it will lock the individual column.

[Indra-db]

ci test, I expect a failure somewhere, I cannot run tests locally due to bake being problematic (see discord)

[Indra-db]

all tests passing 🥳

[Reddy-dev]

ci test, I expect a failure somewhere, I cannot run tests locally due to bake being problematic (see discord)

@Indra-db could you link the message, I think i also have similar issues

[Indra-db]

@Reddy-dev

Tldr, Sander told me to use bake run as opposed to bake test which should fix the ouput

[Indra-db]

@Reddy-dev this was my thread where I was dumping my experience (which I closed)
https://discord.com/channels/633826290415435777/1406452408149741770/1406998533449580585

[Indra-db]

update to latest main

[SanderMertens]

I'm still seeing performance regressions when comparing with latest master:

I think it's better to separate out the implementation into its own functions so there's no risk of regressions.

(Note: benchmarks were done without the FLECS_MUT_ALIAS_LOCKS flag on a regular Flecs master)