doc/dev/Release.md: patch release workflow
We did roughly this today. We put the CHANGELOG.md change in its own MR, so it didn't end up in the tor-llcrypto-v0.4.4 tag. It would have been better to do it the other way so that's what I've documented.
I couldn't test-format this with pandoc because it got tricked by some
of the $
into trying to run TeX.