For #26314 - Configuration paths on OSX can now contain spaces

- Previously, if the configuration was installed to a location that contained spaces in the path on OSX then the tank command would fail to run.
- Updated to check for the required roots.yml config file rather than the now optional templates.yml when determining if a path relates to a pipeline configuration.
Thinking out loud here - I think we support Environment variables inside of the `$parent_location` (e.g. core_Linux, core_Darwin files) - will these still resolve correctly if quoted like this?