Clarify how to override VIVO configuration

[awoods]

There are currently two mechanisms for overriding VIVO configuration:

1. Copying dockercompose.runtime.properties and example.applicationSetup.n3 into the configuration directory (noting that line:35 represents a bug, in that the application configuration directory is actually /usr/local/vivo/home/config and not /usr/local/VIVO/home/config)

• https://github.com/vivo-community/vivo-docker2/blob/master/vivo/Dockerfile#L35-L37

..and

2. Mounting the example-config directory as a volume into /usr/local/vivo/home/config

• https://github.com/vivo-community/vivo-docker2/blob/master/docker-compose.yml#L30

No matter what is written into the files in mechanism (1.) above, it is overwritten by the mounted files in mechanism (2.)

This issue is to resolve the confusion by removing mechanism (1.).