Ensure path components have a separator at runtime

- In our code we use variables to store directory names and then use
  those variables to get specific files via Ti.Filesystem.getFile.

  For example:
  var aFile = Ti.Filesystem.getFile(aDirectory, "file")

  When uglify is run it will convert that line to:
  var aFile = Ti.Filesystem.getFile(__p.file(aDirectory + "file"))

  The problem here is that the variable 'aDirectory' may or may not have
  a trailing path separator but we don't know that until runtime.

  Our fix was to wrap each path component argument passed to
  Ti.Filesystem.getFile in a method that will check at runtime to see if
  the path component ends with a path separator. If it does then we
  don't append anything, if it doesn't then we append a '/'.

  When uglify is run now it will convert the line to:
  var aFile = Ti.Filesystem.getFile(__p.file(__p.endsWithPathSeparator(aDirectory) + "file"))

- Updated the filesystem unit tests to include the addition of
  __p.endsWithPathSeparator.
Add forward slash to each argument in argsToPath

- The argsToPath method now adds a trailing forward slash to each
  argument passed in. This may result in double forward slashes
  in path strings when the application is appified.

- Updated the file method to remove double forward slashes from
  the extension argument at runtime. The method will check to
  see if the extension is a URL and not replace the double
  forward slashes in the scheme portion of the URL (e.g. http://,
  file:///, etc.).
Merge pull request #1 from sztn/path_separator_fix

Path separator fix