Use consistent test site locations in documentation and debug configs

The naming of the test site is inconsistent in the documentation.  Some
parts refer to `gerrit_testsite` while other parts, and the default
debug configurations, refer to `test_site`.

Update the documentation and debug configs to use `gerrit_testsite`.

Change-Id: I5b1fb5c9dcc6c9a39e7d95e88d4e0ea9df384b09

Documentation/dev-readme.txt

@@ -74,7 +74,7 @@ After compiling (above), run Gerrit's 'init' command to create a
 testing site for development use:
 
 ----
-  java -jar buck-out/gen/gerrit.war init -d ../test_site
+  java -jar buck-out/gen/gerrit.war init -d ../gerrit_testsite
 ----
 
 Accept defaults by pressing Enter until 'init' completes, or add
@@ -89,7 +89,7 @@ Shutdown the daemon after registering the administrator account
 through the web interface:
 
 ----
-  ../test_site/bin/gerrit.sh stop
+  ../gerrit_testsite/bin/gerrit.sh stop
 ----
 
 
@@ -120,7 +120,7 @@ The daemon can be directly launched from the build area, without
 copying to the test site:
 
 ----
-  java -jar buck-out/gen/gerrit.war daemon -d ../test_site
+  java -jar buck-out/gen/gerrit.war daemon -d ../gerrit_testsite
 ----
 
 Running the Daemon with Gerrit Inspector
@@ -140,7 +140,7 @@ Gerrit Inspect can be started by adding '-s' option to the
 command used to launch the daemon:
 
 ----
-  java -jar buck-out/gen/gerrit.war daemon -d ../test_site -s
+  java -jar buck-out/gen/gerrit.war daemon -d ../gerrit_testsite -s
 ----
 
 Gerrit Inspector examines Java libraries first, then loads
@@ -168,7 +168,7 @@ The embedded H2 database can be queried and updated from the
 command line.  If the daemon is not currently running:
 
 ----
-  java -jar buck-out/gen/gerrit.war gsql -d ../test_site
+  java -jar buck-out/gen/gerrit.war gsql -d ../gerrit_testsite
 ----
 
 Or, if it is running and the database is in use, connect over SSH