Make geo-postgresql specs track template changes better
#2191 (closed) quietly happened because the
postgresql.conf.erb template changed but the geo-postgresql spec did not detect this. We should refactor the specs so that changing the template will cause a spec failure in the geo-postgresql recipe if the attribute is not added there. Or make reasonable defaults that just work.