Always update ostree refspec when adding remotes.

For a fresh install the ostree origin refspec for the deployed
origin may have a name that doesn't match the remote
names for the ostree content that system has subscribed
to. So, for now, always up the refspec to map the ostree
repo configs we create, so that ostree will find them.

An example of this might be a system that has it's
ostree refspec setup by anaconda to 'ostree-atomic:ostree-atomic-awesome'.
Those names may not map to the names from the product ids installed
on the machine. And if the remote names don't match the
install product names or refspec, we have to pick something.

If there is just one remote, choose it. If there is more than
one, pick the first one sorted by name. For now.

Update unit tests.
Fix odd ostree repo config whitespace issues.

Call iniparse's 'tidy' on the config object before
saving it.
Use iniparse.util.tidy if installed.

Require that version for ostree plugin.
Include 'tls-ca-path' for ostree remote configs.
Remove noise debug logging.
Fix iniparse tidy import.
Reload ostree_config after updating remotes.

This was using stale remotes config info when
attempting to update ostree origin refspec
remote, and not finding the new info.

For the fresh instal cases, the stale config
means no remotes at all, so no attempt to
update refspec.
Merge pull request #985 from candlepin/alikins/ostree_int

Alikins/ostree int