[FR] Multiline (and rich?) yank reason

[webknjaz]

What's the problem this feature will solve?

Having a comprehensive explanation for yanking. I think it is important not to limit the maintainers with a very small input box. It would be useful to be able to show a descriptive message to the end-users too (related to FR #9837).

Describe the solution you'd like

I want <textarea> in the UI, not an <input> (the backend doesn't enforce single-line input here — I verified this by turning it into a textarea w/ DevTools in production).
It could then also be displayed on the individual release pages and only the first line (maybe) would appear in badge tooltips (as suggested in #9837).

Not sure if allowing renderable Markdown would be safe but, I'd at least make the links clickable there too.

Additional context

N/A

[di]

We likely need to set a maximum allowable length for this field on https://peps.python.org/pep-0592/ before being able to support this, as we likely don't want this to be completely unbounded.

[arshm06]

I have submitted my pull request. Thank you!