[core] Revert the link in the priority support ticket description

[michelengelen]

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

just a revert of #10495

[mui-bot]

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

Generated by 🚫 dangerJS against 25af267

[DanailH]

One note regarding the prefixes for the PR titles - for things that are not related to a particular component or deal with the component internals we use [core]. for docs there is the [docs] and then we have [test] and the localization one. Based on this the script for the changelog works the way it does now. Now, if there is a need we can always add more descriptive prefixes but for now the ones we have seem enough.

[oliviertassinari]

for things that are not related to a particular component or deal with the component internals we use [core]

@DanailH I wonder if we should create a new scope soon or later, I'm not sure exactly how to call it: support-infra, community-infra, contribution-infra. We will see if this becomes frequent enough to make a scope of effective (a good way to discriminate between issues/PRs). I could see there stuff around maximizing issues, maximizing PRs. But maybe it's too early, it would be a too small of a scope for a GitHub label (core being it's parent).

[DanailH]

@oliviertassinari good point. We can just call it [infra], although it might be difficult to differentiate [core] and [infra].

[michelengelen]

@DanailH @oliviertassinari IMO we could be good with just using [infra]. I dont see a particular problem differentiating this. My suggestion would be:

• [core] is anything related to the codebase structure, e.g. packaging, general refactors, etc.
• [infra] could be a subset of that specifically for infrastructural changes, e.g. github templates, github actions, CI, etc.