[infra] Adjust the links to search for issues

[michelengelen]

• [x] I have followed (at least) the PR section of the contributing guide.

---

I noticed that the link in the issues templates leads to the default issue search, which looks for is:issue and is:open. Since the solution could also be in a closed issue this should be adjusted.

One question remains: should we mention in the text that there could also be a closed issue with a solution as well? 🤔

[mui-bot]

Deploy preview: https://deploy-preview-11995--material-ui-x.netlify.app/

Updated pages:

• docs/data/introduction/support/support.md

Generated by :no_entry_sign: dangerJS against e738f4185545eddb6065a7400ed10319e1599dbb

[oliviertassinari]

I really wonder if we shouldn't create a new label for all of this type of work. Like a [devex-infra] label, or [support-infra], [product-infra]. For now, [core] is ok, but it's not [code-infra] or [docs-infra].

Otherwise, how about this: We introduce abroad [infra] level, it's like [core] but shared across repositories, and it's a catch-all until there is a clear pattern to specialize [code-infra] and [docs-infra] are specialization examples). https://www.notion.so/mui-org/scope-infra-c446897d1449403ea7ffe076ddedc00a

[michelengelen]

On another note: we could probably add org templates instead, if we would be willing to give up the custom names.

I was reading about this today and it might be a good way of reducing maintenance work!

[oliviertassinari]

add org templates

@michelengelen agree, we should explore this. The related issues: https://github.com/mui/mui-private/issues/386, https://github.com/mui/mui-private/issues/360.