[infra] Fix support tier-1 flow regression

[oliviertassinari]

I have noticed this from #1148. The support flow seems to have had a couple of problems with #985. This PR aims to go after 1.

1. https://www.notion.so/mui-org/GitHub-community-issues-PRs-Tier-1-12a84fdf50e44595afc55343dac00fca no longer working, added the status: waiting for maintainer label back in
2. Bug reports no longer prompt developers to provide the exact version of their dependencies @mui/envinfo. [envinfo] Ask for output from envinfo in issues material-ui#23881
3. Bug reports and issue reports have a redundant H1, e.g. [accordion] <summary> / <details> based implementation #1148
4. We no longer have the "Search keywords". Added in [core] Update issue actions & templates mui-x#10375 because it started to be really hard to find duplicate issues
5. https://discord.com/channels/1287292451308048406/1287292451308048409 link doesn't work. If we link to Discord, I think [docs] Avoid broken link material-ui#38154 will avoid leaving breadcrumbs of broken links.

On using issue templates (now in Base UI, React, Tailwind CSS) vs. issue forms (Next.js, React Aria). I'm biased for issue forms, since mui/mui-x#2468. But happy either way. It feels like once we become tired of developers opening issues without respecting what we ask for, we will naturally land on issue forms.

[flaviendelangle]

We no longer have the "Search keywords". Added in mui/mui-x#10375 because it started to be really hard to find duplicate issues

I suspect it has been removed after https://mui-org.slack.com/archives/C02P87NQLJC/p1733997960666959

[mui-bot]

Netlify deploy preview

https://deploy-preview-1149--base-ui.netlify.app/

Generated by 🚫 dangerJS against 5851c67

[michelengelen]

Why have the labels been removed in the first place? And shouldn't we also add the default labels, like bug, feature to the respective templates as well? 🤔