Try to disambiguate the Bug issue template

Signed-off-by: Rémy Coutable <remy@rymai.me>

.gitlab/issue_templates/Bug.md

@@ -6,13 +6,13 @@
 (How one can reproduce the issue - this is very important)
-### Expected behavior
-(What you should see instead)
-### Actual behavior
-(What actually happens)
+### What is the current *bug* behavior?
+(What actually happens)
+### What is the expected *correct* behavior?
+(What you should see instead)
 ### Relevant logs and/or screenshots
@@ -23,23 +23,23 @@ logs, and code as it's very hard to read otherwise.)
 (If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
-#### Results of GitLab application Check
+#### Results of GitLab environment info
 (For installations with omnibus-gitlab package run and paste the output of:
-`sudo gitlab-rake gitlab:check SANITIZE=true`)
+`sudo gitlab-rake gitlab:env:info`)
 (For installations from source run and paste the output of:
-`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
-
-(we will only investigate if the tests are passing)
-#### Results of GitLab environment info
+`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
+#### Results of GitLab application Check
 (For installations with omnibus-gitlab package run and paste the output of:
-`sudo gitlab-rake gitlab:env:info`)
+`sudo gitlab-rake gitlab:check SANITIZE=true`)
 (For installations from source run and paste the output of:
-`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)
+`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`)
+
+(we will only investigate if the tests are passing)
 ### Possible fixes