Add "Rendered" link to RFC MRs

Unless I'm missing something, it's currently quite annoying to get to an open RFC's rendered markdown. I know of two ways:

1. Click on "Changes", then the three dots on the file's diff, then "View file @ [commit]"
2. Click on the source branch, and manually navigate to the RFC's file in the browser

Rust's and Matrix' (random examples) RFC process has a nice solution to this, which is to add a "Rendered" link to the MR description, which links to the /blob/ in the source branch (example for !32 (merged): https://gitlab.archlinux.org/dvzrv/rfcs/-/blob/rfc/arch_linux_ports/rfcs/0032-arch-linux-ports.rst). Is it possible to adopt this convention for Arch's RFCs as well?

changed the description

...and I only just now realized that the files are actually RST, not markdown, and GitLab has a hard time rendering them correctly. I guess it's not as easy then, because something would need to serve each fork's generated hugo content.

Is there any issues with how gitlab previews the rst files?

Usually the people doing the RFC just add the link to the gitlab preview like it was done here: !26 (merged)

There isn't a problem with how they are rendered, but I did just look and out of the 7 open MRs none have a direct link to the file.

For what it's worth, there's a pending RFC about streamlining the writing process for RFCs, which implies to switch to markdown (among other stuff).