feat: ecsact codegen plugin for optimization

[zaucy]

No description provided.

[cocogitto-bot]

❌ Found 14 compliant commit and 3 non-compliant commits in b8cecbe.

Commit 039dbfb by @Kelwan is not conform to the conventional commit specification :

• message: finish context_add, beginning work on dynamic library calls
• cause:

  Missing commit type separator `:`
  
  Caused by:
       --> 1:7
        |
      1 | finish context_add, beginning work on dynamic library calls
        |       ^---
        |
        = expected scope or type_separator
  

Commit 6798356 by @Kelwan is not conform to the conventional commit specification :

• message: Fix some line endings
• cause:

  Missing commit type separator `:`
  
  Caused by:
       --> 1:4
        |
      1 | Fix some line endings
        |    ^---
        |
        = expected scope or type_separator
  

Commit 631ca1e by @Kelwan is not conform to the conventional commit specification :

• message: All context implentations done. Adding markers then moving to testing
• cause:

  Missing commit type separator `:`
  
  Caused by:
       --> 1:4
        |
      1 | All context implentations done. Adding markers then moving to testing
        |    ^---
        |
        = expected scope or type_separator
  

[zaucy]

just a few small changes. I haven't fully read it yet. I'll need to run it locally and see the codegen.

One thing I noticed is we're not 'preparing' any of the storages on create registry. We need to do that because otherwise EnTT will generate storage on the fly. This could cause an issue if we run anything in parallel or access storage part way through an iteration conditionally.

you can prepare a storage by simply doing registry.storage<T>(); and assign it to no variable. Simply calling storage "prepares" it. We should do that in ecsact_create_registry.

In the old code it was in init_registry. As you can see it's 'preparing' each storage ahead of time. It gets called when a registry is created and when it's cleared.