PR: Update RELEASE.md for 1.x version

[dalthviz]

Update RELEASE.md following current branch structure (master and 1.x) and add some missing info

[CAM-Gerlach]

Per discussion with @dalthviz , given there are some important additions here that would be very useful in master as well, and the structure and formatting is a lot better than what I originally did, I'm going to integrate the master changes in here and fix a few typos/grammar issues, so we can then non-null merge all these improvements to master with just a find-replace of 1.x to master and tweaking the package build line. Marking it as draft until that's done...

[CAM-Gerlach]

Thanks @dalthviz for the great improvements! LGTM now that I synced the additions and improvements with those in master, minus a few master-specific things. @ccordoba12 and @dalthviz , would you mind reviewing? Once this is ready, I can take care of the merge, as there are a few things (a couple more than I initially thought) that I'll need to take care of when merging to master. Thanks!

[dalthviz]

Thanks @CAM-Gerlach for the changes! LGTM 👍

[ccordoba12]

Looks good to me, thanks @dalthviz and @CAM-Gerlach!

[dalthviz]

You will take care of the merge with master right @CAM-Gerlach ?

[CAM-Gerlach]

Yup, in work now

[dalthviz]

Just in case @CAM-Gerlach I merged #278 (maybe that can affect the merge you started doing 😅 )

[CAM-Gerlach]

Yeah, you could say it "affected" it...if by "affected" you mean blocked me when I tried to push and forced me to start over since it created new commits on upstream between the time I started the merge and when I finished 😆

It wasn't that bad, I did some juGitsu and managed to not have to do everything over, just the Git parts haha, just FYI next time let's maybe not merge something to master at the same time, hmm? 😉

[CAM-Gerlach]

In all seriousness, it took me longer to write that than actually fix the problem jaja, no worries

[CAM-Gerlach]

Also, separately merged the release per the new release guide