Upgrade Esmond to use PostgreSQL 10 instead of 9.

[mfeit-internet2]

Having both causes a conflict when installing the toolkit because pScheduler expects 10 to be running.

[mfeit-internet2]

This is in the issue-160 branch. Handing off to Andy for test and merge.

[mfeit-internet2]

@arlake228 When you get back:

I did some additional cleanups to the build that are sitting in a reconstituted issue-106.

When the RPM is installed on the build system, it was missing python36-django and python36-django-tastypie as dependencies. On a fresh system with the EPEL and perfSONAR repos, I get this:

[root@scratch vagrant]# yum -y install esmond-4.3.0-0.a1.0.el7.x86_64.rpm > /tmp/junk
Error: Package: esmond-4.3.0-0.a1.0.el7.x86_64 (/esmond-4.3.0-0.a1.0.el7.x86_64)
           Requires: mod_wsgi >= 4.6.5
           Available: mod_wsgi-3.4-18.el7.x86_64 (base)
               mod_wsgi = 3.4-18.el7
           Available: mod_wsgi-4.6.4-1.el7.x86_64 (perfSONAR)
               mod_wsgi = 4.6.4-1.el7
Error: Package: esmond-4.3.0-0.a1.0.el7.x86_64 (/esmond-4.3.0-0.a1.0.el7.x86_64)
           Requires: python3-thrift
Error: Package: esmond-4.3.0-0.a1.0.el7.x86_64 (/esmond-4.3.0-0.a1.0.el7.x86_64)
           Requires: python3-memcached
Error: Package: esmond-4.3.0-0.a1.0.el7.x86_64 (/esmond-4.3.0-0.a1.0.el7.x86_64)
           Requires: python3-pycassa

[laeti-tia]

@mfeit-internet2 depending on the yum setup, it might be expected. Those package are coming from our own repository and are currently only in the nightly repo (or at least it was like that a few weeks ago when I worked on it). Which pS repo is the install machine using?