Update network/filesharing configuration to allow running against locally built modules from Okapi

A module running on the host needs to be able to connect to the Okapi hosted within the VM. The connection needs to be bidirectional. meaning Okapi needs to be able to make the calls outside of the VM, addressing the module running on the host machine.

The proposed forward port range is 8081-9000

Another solution (per Adam) to this problem is to cross the local machine/VM boundry by running a local instance of Okapi that talks to the Okapi running within the VM. This is not, however, the solution we are going to pursue here

This work should directly support STCLI-114.

Acceptance criteria:

• port forwarding configuration for Vagrant that allows communication between a local module instance and Okapi