Update docs for testing common requirejs tests

docs/en_us/internal/testing.rst

@@ -278,6 +278,7 @@ console::
     paver test_js_run -s cms-squire
     paver test_js_run -s xmodule
     paver test_js_run -s common
+    paver test_js_run -s common-requirejs
 
 To run JavaScript tests in your default browser::
 
@@ -287,6 +288,7 @@ To run JavaScript tests in your default browser::
     paver test_js_dev -s cms-squire
     paver test_js_dev -s xmodule
     paver test_js_dev -s common
+    paver test_js_dev -s common-requirejs
 
 These paver commands call through to a custom test runner. For more
 info, see `js-test-tool <https://github.com/edx/js-test-tool>`__.
@@ -608,4 +610,3 @@ Acceptance Test Techniques
    and "LMS" when they follow this convention: name your feature in the
    .feature file CMS or LMS with a single period and then no other
    periods in the name. The name can contain spaces. E.g. "CMS.Sign Up"
-