Fixing fetch.py execution on Windows due to path issues, ensuring lookups directory always exists
Changes to enable Boundary Splunk integration to work on Windows - Fixing path issues calling fetch.py (by using full path including $SPLUNK_HOME env var) - Adding empty 'lookups' directory to prevent manually having to create it - Updating setup script t

Test Plan: Installed on Windows environment running in EC2, confirmed fetch.py runs at set interval and setup page updates boundary.xml with ORG_ID

Reviewers: philip

Differential Revision: http://phabricator.cid1.boundary.com/D965
Updating boundary setup script based on feedback, improved readability of file editing logic and changed reference to SPLUNK_HOME to cause error if unset