[RFC] Restructure/update Release Specs about release-specs HOT 2 OPEN

I agree that we should rework the release spec tests.

One thing would be to parameterize the DUT as a generic board and specify "golden" boards, which would not really be the thing we are testing.

The most challenging example of this would be multihop, where the solution would be have 3 tests, one with the DUT as a root node, then as a middle node, then as end node.

We should also have a nice breakdown of the boards that were run through these tests, making sure that every board in the list would have undergone all applicable tests. Then we can enter that in the release notes very clearly and simply so that people know what "should" be passing for a given release.

The final thing would be to create a tracking issue for the specific release that exists in RIOT for all bugs found that would not be blocking the release (the compile_and_test_for_board.py might be hard to get everything passing but shouldn't block the release).

from release-specs.

We should also collect the test artifacts and add it as an asset to the release... I don't know how long the retention time is for the actions logs.

from release-specs.