Support built-in restrictions for component combination

Summary

It would be helpful to have a system to restrict which components combination can be passed as parameter to a system. This is to avoid cases where a malicious actor could use in the same transactiom a Game's data in combination with another unrelated game's metadata. Making the whole system logic running on bogus assumptions.

Details

An good example of this can be found in the Tic-Tac-Toe blog example:
https://blog.magicblock.gg/bolt-tic-tac-toe/

In this example: If a malicious actor passes a Grid component in combination with an unrelated Players component, a user could effectively play someone else's game.

Start by reviewing how component parameters are handled and the Tic-Tac-Toe blog example linked in the issue. Clarify the intended restriction model and identify how unrelated Grid and Players components could be detected. Done means the system prevents invalid component combinations from being accepted in a transaction.