Problem: No automated way to set up a dev/test network (#2300)

* Problem: No automated way to set up a dev/test network

* Problem: docs not updated for stack, ansible and docker based dev environments

* Problem: Using apt triggers java runtime installation on MacOS

- Update pre_tasks in ansible
- Update bigchaindb-stop playbook to handle pre_tasks

* Update Tendermint version to 0.19.3 from 0.19.2

* Update tendermint version to 0.19.3 everywhere else

* Problem: Sphinx warns about duplicate section labels

Solution: Don't use sphinx.ext.autosectionlabel

* Problem: Sphinx complains that run-node-with-docker not in any TOC

Solution: Add run-node-with-docker to a TOC (i.e. to an index.rst file)

* Tendermint has not tagged `0.19.3` container

* Problem: Internal hyperlinks to new pages not working

Solution: Add .html to the ends of the filename strings

* Problem: Invalid script imports

* Problem: Invalid comparison for supported OS version

* Addressing comments I

* Problem: No way to configure dev/forked repo for developers

* Problem: Docs not updated with STACK_REPO parameter

* Addressing comments II

docs/contributing/source/dev-setup-coding-and-contribution-process/write-code.rst

@@ -97,13 +97,15 @@ framework to write Python tests. Read all about it.
 Most tests are in the ``tests/`` folder. Take a look around.
 
 
-Running a Local Node for Dev and Test
--------------------------------------
+Running a Local Node/Network for Dev and Test
+---------------------------------------------
 
 This is tricky and personal. Different people do it different ways. We documented some of those on separate pages:
 
 - `Dev node setup and running all tests with Docker Compose <run-node-with-docker-compose.html>`_
 - `Dev node setup and running all tests as processes <run-node-as-processes.html>`_
+- `Dev network setup with stack.sh <run-dev-network-stack.html>`_
+- `Dev network setup with Ansible <run-dev-network-ansible.html>`_
 - More to come?