Kernel developer: "steps to reproduce" in regression report

**As a kernel developer, I want to have clear and straightforward instructions about how to reproduce a bug so I can test and investigate it more easily.**

## Background
One of the key goals of regression reports should be to be directly useful for the developers. Notifying the developers about regressions is only the first step in a process that should involve more work on the reporter side to bridge the gap between the CI tool and the developer's involvement in the fix.

Most of the time, reproducing a bug is the starting point to investigate it. If the task of setting up a test setup, building the necessary images, filesystems and the rest of the test components is left to the developers it'll be very hard to get them engaged and gain traction. If the reports could give very clear and foolproof instructions about how to reproduce the bug in a local or remote setup, it'll be easier to convince the developers to work on a fix.

No files, tests, or entry points are named. Start by reviewing the regression-report workflow and how reproduction information is currently presented; done means reports provide clear, straightforward instructions for reproducing the reported bug in a local or remote setup.

Written by the indexing model from the issue text.