Rethink `useTresReady`

[alvarosabu]

Description

As a maintainer of TresJS, I would like to improve the naming and practices used for the useTresReady composable, which is a mix of a composable and a lifecycle hook and see if the usercase is relevant

Suggested solution

Rethink https://github.com/Tresjs/tres/blob/main/src/composables/useTresReady/index.ts

Alternative

No response

Additional context

#712

Validations

• [x] I agree to follow this project's Code of Conduct
• [x] Read the Contributing Guidelines.
• [x] Read the docs.
• [x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[Tinoooo]

In the scope of this issue we should cleanup the composable calls in event callbacks. This already leads to an onUnmounted call when there is not component instance yet. See console warning.

[Tinoooo]

@alvarosabu Before this PR, there was logic that assumed the renderer would be ready after 100 ms, as Tres was considered "degenerate." What does this mean and do we still need it?