- fix doc references, refactor fixtures docs to more quickly start

with examples instead of big text blobgs
- also silence -q and -qq reporting some more

doc/en/example/parametrize.txt

@@ -36,7 +36,6 @@ we parametrize two arguments of the test function so that the test
 function is called three times.  Let's run it::
 
     $ py.test -q 
-    collecting ... collected 3 items
     ..F
     ================================= FAILURES =================================
     ____________________________ test_eval[6*9-42] _____________________________
@@ -54,7 +53,6 @@ function is called three times.  Let's run it::
     E        +  where 54 = eval('6*9')
     
     test_expectation.py:8: AssertionError
-    1 failed, 2 passed in 0.02 seconds
 
 As expected only one pair of input/output values fails the simple test function.
 
@@ -94,15 +92,12 @@ Now we add a test configuration like this::
 This means that we only run 2 tests if we do not pass ``--all``::
 
     $ py.test -q test_compute.py
-    collecting ... collected 2 items
     ..
-    2 passed in 0.01 seconds
 
 We run only two computations, so we see two dots.
 let's run the full monty::
 
     $ py.test -q --all
-    collecting ... collected 5 items
     ....F
     ================================= FAILURES =================================
     _____________________________ test_compute[4] ______________________________
@@ -114,7 +109,6 @@ let's run the full monty::
     E       assert 4 < 4
     
     test_compute.py:3: AssertionError
-    1 failed, 4 passed in 0.02 seconds
 
 As expected when running the full range of ``param1`` values
 we'll get an error on the last one.
@@ -157,22 +151,20 @@ this is a fully self-contained example which you can run with::
 
     $ py.test test_scenarios.py
     =========================== test session starts ============================
-    platform linux2 -- Python 2.7.3 -- pytest-2.3.0.dev14
-    plugins: xdist, bugzilla, cache, oejskit, cli, timeout, pep8, cov
-    collecting ... collected 4 items
+    platform linux2 -- Python 2.7.3 -- pytest-2.3.0.dev19
+    collected 4 items
     
     test_scenarios.py ....
     
-    ========================= 4 passed in 0.02 seconds =========================
+    ========================= 4 passed in 0.01 seconds =========================
 
 If you just collect tests you'll also nicely see 'advanced' and 'basic' as variants for the test function::
 
 
     $ py.test --collectonly test_scenarios.py
     =========================== test session starts ============================
-    platform linux2 -- Python 2.7.3 -- pytest-2.3.0.dev14
-    plugins: xdist, bugzilla, cache, oejskit, cli, timeout, pep8, cov
-    collecting ... collected 4 items
+    platform linux2 -- Python 2.7.3 -- pytest-2.3.0.dev19
+    collected 4 items
     <Module 'test_scenarios.py'>
       <Class 'TestSampleWithScenarios'>
         <Instance '()'>
@@ -233,24 +225,22 @@ Let's first see how it looks like at collection time::
 
     $ py.test test_backends.py --collectonly
     =========================== test session starts ============================
-    platform linux2 -- Python 2.7.3 -- pytest-2.3.0.dev14
-    plugins: xdist, bugzilla, cache, oejskit, cli, timeout, pep8, cov
-    collecting ... collected 2 items
+    platform linux2 -- Python 2.7.3 -- pytest-2.3.0.dev19
+    collected 2 items
     <Module 'test_backends.py'>
       <Function 'test_db_initialized[d1]'>
       <Function 'test_db_initialized[d2]'>
     
-    =============================  in 0.01 seconds =============================
+    =============================  in 0.00 seconds =============================
 
 And then when we run the test::
 
     $ py.test -q test_backends.py
-    collecting ... collected 2 items
     .F
     ================================= FAILURES =================================
     _________________________ test_db_initialized[d2] __________________________
     
-    db = <conftest.DB2 instance at 0x17dd440>
+    db = <conftest.DB2 instance at 0x13dc9e0>
     
         def test_db_initialized(db):
             # a dummy test
@@ -259,7 +249,6 @@ And then when we run the test::
     E           Failed: deliberately failing for demo purposes
     
     test_backends.py:6: Failed
-    1 failed, 1 passed in 0.01 seconds
 
 The first invocation with ``db == "DB1"`` passed while the second with ``db == "DB2"`` failed.  Our ``pytest_funcarg__db`` factory has instantiated each of the DB values during the setup phase while the ``pytest_generate_tests`` generated two according calls to the ``test_db_initialized`` during the collection phase.
 
@@ -302,19 +291,17 @@ Our test generator looks up a class-level definition which specifies which
 argument sets to use for each test function.  Let's run it::
 
     $ py.test -q
-    collecting ... collected 3 items
     F..
     ================================= FAILURES =================================
     ________________________ TestClass.test_equals[1-2] ________________________
     
-    self = <test_parametrize.TestClass instance at 0x19a6d88>, a = 1, b = 2
+    self = <test_parametrize.TestClass instance at 0x23ea170>, a = 1, b = 2
     
         def test_equals(self, a, b):
     >       assert a == b
     E       assert 1 == 2
     
     test_parametrize.py:18: AssertionError
-    1 failed, 2 passed in 0.02 seconds
 
 Indirect parametrization with multiple resources
 --------------------------------------------------------------
@@ -333,8 +320,6 @@ with different sets of arguments for its three arguments:
 Running it results in some skips if we don't have all the python interpreters installed and otherwise runs all combinations (5 interpreters times 5 interpreters times 3 objects to serialize/deserialize)::
 
    . $ py.test -rs -q multipython.py
-   collecting ... collected 75 items
    ............sss............sss............sss............ssssssssssssssssss
    ========================= short test summary info ==========================
    SKIP [27] /home/hpk/p/pytest/doc/en/example/multipython.py:21: 'python2.8' not found
-   48 passed, 27 skipped in 3.11 seconds