docs: Update kernel issue reporting guidance

All four AskingQuestions copies direct users to the removed top-level
Linux REPORTING-BUGS file. They also present reports built around Linux
2.6, procfs and obsolete module names without an age marker.

Point each copy at
Documentation/admin-guide/reporting-issues.rst, the current kernel
reporting guide. Keep the old reports as examples of useful diagnostic
detail, but label them historical so their commands are not reused as
SCST setup instructions.

AskingQuestions

@@ -24,8 +24,9 @@ So, as a bottom line, don't ask questions answers on which you can find
 out yourself by a simple documentation reading and minimal thinking
 effort.
 
-If you experience kernel crash, hang, etc., you should follow
-REPORTING-BUGS file from your kernel source tree.
+If you experience a kernel crash, hang, etc., follow
+Documentation/admin-guide/reporting-issues.rst from the current kernel
+source tree in addition to the SCST-specific guidance below.
 
 For most questions it is very desirable if you attach to your message
 full kernel log from the target since it's booted. Note, *SINCE IT
@@ -73,6 +74,10 @@ didn't bothered to look in the kernel log, where, very probably, the
 reason of the error was logged.
 
 
+The reports below are preserved as examples of useful problem detail.
+Their kernel versions, module names, paths and configuration commands
+are historical and must not be used as setup instructions.
+
 Here are three examples of good questions:
 
 ======================================================================

iscsi-scst/AskingQuestions

@@ -24,8 +24,9 @@ So, as a bottom line, don't ask questions answers on which you can find
 out yourself by a simple documentation reading and minimal thinking
 effort.
 
-If you experience kernel crash, hang, etc., you should follow
-REPORTING-BUGS file from your kernel source tree.
+If you experience a kernel crash, hang, etc., follow
+Documentation/admin-guide/reporting-issues.rst from the current kernel
+source tree in addition to the SCST-specific guidance below.
 
 For most questions it is very desirable if you attach to your message
 full kernel log from the target since it's booted. Note, *SINCE IT
@@ -73,6 +74,10 @@ didn't bothered to look in the kernel log, where, very probably, the
 reason of the error was logged.
 
 
+The reports below are preserved as examples of useful problem detail.
+Their kernel versions, module names, paths and configuration commands
+are historical and must not be used as setup instructions.
+
 Here are three examples of good questions:
 
 ======================================================================

qla2x00t/qla2x00-target/AskingQuestions

@@ -24,8 +24,9 @@ So, as a bottom line, don't ask questions answers on which you can find
 out yourself by a simple documentation reading and minimal thinking
 effort.
 
-If you experience kernel crash, hang, etc., you should follow
-REPORTING-BUGS file from your kernel source tree.
+If you experience a kernel crash, hang, etc., follow
+Documentation/admin-guide/reporting-issues.rst from the current kernel
+source tree in addition to the SCST-specific guidance below.
 
 For most questions it is very desirable if you attach to your message
 full kernel log from the target since it's booted. Note, *SINCE IT
@@ -73,6 +74,10 @@ didn't bothered to look in the kernel log, where, very probably, the
 reason of the error was logged.
 
 
+The reports below are preserved as examples of useful problem detail.
+Their kernel versions, module names, paths and configuration commands
+are historical and must not be used as setup instructions.
+
 Here are three examples of good questions:
 
 ======================================================================

scst/AskingQuestions

@@ -24,8 +24,9 @@ So, as a bottom line, don't ask questions answers on which you can find
 out yourself by a simple documentation reading and minimal thinking
 effort.
 
-If you experience kernel crash, hang, etc., you should follow
-REPORTING-BUGS file from your kernel source tree.
+If you experience a kernel crash, hang, etc., follow
+Documentation/admin-guide/reporting-issues.rst from the current kernel
+source tree in addition to the SCST-specific guidance below.
 
 For most questions it is very desirable if you attach to your message
 full kernel log from the target since it's booted. Note, *SINCE IT
@@ -73,6 +74,10 @@ didn't bothered to look in the kernel log, where, very probably, the
 reason of the error was logged.
 
 
+The reports below are preserved as examples of useful problem detail.
+Their kernel versions, module names, paths and configuration commands
+are historical and must not be used as setup instructions.
+
 Here are three examples of good questions:
 
 ======================================================================