Select Components not disabled when waiting for interaction response

[MeguminSama]

Description

If you have an interaction with buttons and a select menu, and you click a button, while all the buttons will be in a disabled state, the dropdown can still be opened, modified, and submitted.

I've encountered some race condition-y things because of this unexpected behaviour.

Steps to Reproduce

1. Create a message with at least one button component and one select component.
2. Click on a button. The buttons should all be in a disabled state while waiting for the interaction response.
3. Notice that the select menu can still be opened, edited, and submitted, all while still waiting for the previous interaction response.

Expected Behavior

Select Components should be disabled when waiting for an interaction response, just as buttons currently do.

Current Behavior

Select component remains selectable, editable, and submitable when waiting for an interaction response. This is different to the behaviour for buttons.

Screenshots/Videos

Client and System Information

Stable 121760 (a52cee9) Host 1.0.9004 Windows 10 64-Bit (10.0.22000)

~~You can test this yourself with the /builder command for the bot used in the example gif, available here: https://discord.com/api/oauth2/authorize?client_id=887871674672906260&permissions=268460032&scope=bot%20applications.commands~~

The bot is dead now but it should be easy to reproduce still.