[chore] Clarify reason for Servlet API deprecations

Author: chadlwilson

src/main/java/org/jruby/rack/servlet/DefaultServletRackContext.java

@@ -148,17 +148,17 @@ public RequestDispatcher getNamedDispatcher(String name) {
         return context.getNamedDispatcher(name);
     }
 
-    @Override @Deprecated
+    @Override @Deprecated // Deprecated in API parent
     public Servlet getServlet(String name) throws ServletException {
         return context.getServlet(name);
     }
 
-    @Override @Deprecated
+    @Override @Deprecated // Deprecated in API parent
     public Enumeration<Servlet> getServlets() {
         return context.getServlets();
     }
 
-    @Override @Deprecated
+    @Override @Deprecated // Deprecated in API parent
     public Enumeration<String> getServletNames() {
         return context.getServletNames();
     }
@@ -198,7 +198,7 @@ public String getServletContextName() {
         return context.getServletContextName();
     }
 
-    @Override @Deprecated
+    @Override @Deprecated // Deprecated in API parent
     public void log(Exception e, String msg) {
         logger.log(msg, e);
     }

src/main/java/org/jruby/rack/servlet/ResponseCapture.java

@@ -81,9 +81,9 @@ public void setStatus(int status) {
         }
     }
 
-    @SuppressWarnings("deprecation")
     @Override
-    @Deprecated
+    @Deprecated // Deprecated in API parent
+    @SuppressWarnings("deprecation")
     public void setStatus(int status, String message) {
         if ( handleStatus(status, false) ) {
             super.setStatus(status, message);