Add a permission filter to message components

[Mehgugs]

Currently, there is a permission which controls whether users can execute application commands (this includes slash commands and context menu commands) however, there is no equivalent for message components. I think it would be a worthwhile improvement if components could have an optional field which prevents them being interacted with by users/roles/permissions... that don't match.

I think being able to exclude/include people from using components would improve the current user experience a lot, often components simply ignore or fall through when a user interacts with them who is not supposed to. I have personally used many bots where the buttons are clunky because of the edge cases bots are forced to deal with regarding who can interact with them.

• But bots can already filter reactions on their end.
  This is true, but buttons still appearing to work for users and silently failing is not desirable and ephemeral "Sorry you cannot use this button" responses are unsightly. Application commands were also filterable on the bot side, but part of permissions v2 is specifically to make that part of the built in behaviour and improve how they appear to end users.

• If you only want certain people to see a component, control where/who the message is sent to.
  There are many cases in which an ephemeral message/private thread/channel is not sufficient or even overkill. This also assumes that the filtered users won't change after the component has been sent.

[Mehgugs]

It seems there's an old post from the 11th June 2021!! #3344, however the scope of my proposal is a bit clearer, so I'd like to keep this open.