Set "known good" portal version

Rather than use the latest version, we set a particular version for the
portal code. Updating to newer versions can then be tested before being
committed. This ensures we always have a "known good" configuration, if
problems are introduced in later versions, especially conflicts between
Ansible and the portal code, which cannot be picked up by developers not
using Ansible.
Remove modified seed file and ensure completion

Our seed file, required for the earlier portal, overwrites the seed file
required by the new portal. So, stop doing that.  (We may need to setup
the R server some other way, though).

Also, ensure a failure to stop Solr, due to Solr not running, cannot cause
the deployment to fail.