Top-level components are not necessarily action rows

[advaith1]

looks like people were writing code that assumes that top-level components are always action rows, but that is not the case. unfortunately we were saying this in the docs, so removing that

[ManHatos]

When are they not action rows?

[advaith1]

currently all components bots can send need to be in action rows. however the new content inventory component (from the new activity cards feature) is not in an action row, and future display components for bot UIs will not use action rows.

[Rapptz]

This is a breaking change risk for a few libraries, including discord.py (for sending, not receiving). I'm mentioning it here instead of Discord just so there's a paper trail for the statement. Whether the change is for the receiving end, the sending end, or both varies but either way this change can break things.

[Bilal2453]

A bit less important library here, but this also completely breaks sending this component in my library, which pretty much hardcodes the action row requirement in the logic. On the receiving end it was annoying enough I provide an almost raw structure to the user, but most of my users also assume an action row always exists, completely breaking their code.