All nodes are renderable

[chiefcll]

I was looking to fix: #463 and noticed it wasn't happening any longer in main. This is because all nodes are now renderable due to
https://github.com/lightning-js/renderer/blob/main/src/core/CoreNode.ts#L771

Every node is being given a texture making it renderable. I assume you don't want that to be the case as every container node is now being rendered.

For instance:

const yellowRect = renderer.createNode({
    x: 300,
    y: 0,
    width: 100,
    height: 100,
    color: 0x00000000,
    parent: testRoot,
  });

Gets the defaultTexture, even though it shouldn't be rendered.

[wouterlucas]

You’re correct that we don’t need to provide a default texture for nodes without renderable properties. This will be adjusted to align with the renderable properties, but that section will also need updates to reflect recent texture throttling changes.

The broader issue here is that isRenderable is currently used to indicate both "can this be rendered?" and "is it ready to be rendered?" Previously, these were the same since a node could be added to the render pipeline, and its texture would load during the addQuads step without throttling.

With recent changes, textures can now load asynchronously and may be queued to manage frame-by-frame texture processing limits. This means isRenderable will likely need to represent states like not-renderable, pending, and renderable to accommodate the asynchronous pipeline.

I’d recommend holding off on addressing the color issue until 2.9.0 is stable, as these changes will likely resolve related problems.