Update how we do release documentation

Will include tests on real hardware. The current RELEASES description can probably be explicit on how we're testing as well, e.g., refer to CI, docs on real hw tests, etc. Goal: someone else can repeat it (which also means someone else can understand it, suggest improvements, etc).

Will also include signing the release tarball with a TKey.