Issue template: move reproduction steps to the top

[Janpot]

Following up on mui/mui-toolpad#908 which proposes to experiment with this in the core repo first.

When creating issues an issue I tend to

1. describe the steps that lead me to the situation
2. explain what's buggy about it
3. explain what the correct behavior may be

in that order. However, the issue template puts 1. after 3. Whenever I file a core bug report, it feels like the issue template works against me.

[mui-bot]

No bundle size changes

Generated by 🚫 dangerJS against 0ffbb92

[oliviertassinari]

To further precise the pain point, I think that it's a matter of: who we optimize for:

• The current issue template feels optimized for maintainers. You first want to see what's wrong/expected, to get some intuition on what the issue is about. It's only then that you will look at the reproduction in case you have a doubt.
• However, as a developer, when you create an issue, it feels backward. I don't know about you, but when I create an issue, I have to force myself to move content out of the actual behavior to the reproduction steps.

No objections to trying this change.

[michaldudak]

I guess it depends on the person. I prefer to explain what's wrong first, then describe how to get there. I'm ok with trying another approach, though.

[oliviertassinari]

@michaldudak How do this experimentation go over the last few weeks?

[michaldudak]

Both approaches are equally fine for me, so we can choose the one that suits the rest of the team better.

[oliviertassinari]

Ok, added this as a potential topic for next week https://www.notion.so/mui-org/8cf5ff4498e94053b54f3199a0f5b745?v=51a3c47493c744eea62559058824c5fc&p=0566064ded784ef786b163b1c8dff280&pm=s