Support the Integration of Remote Results Files That Are Available through HTTP

[gkapfham]

Right now the chasten integrate command only allows the specification of one
or more result local files on the command-line. This means that if there are,
for instance, results files in a remote GitHub repository a person who wants to
perform the integration step must first clone the GitHub repository and then
type all of the directory names when running the chasten integrate command.

Ultimately, it would be nice if all of the various paths that chasten supports
for input could either be a file name, directory, or remote file name. Which one
of these it actually is should be automatically detected by the tool! This means
that, for instance, the tool should never crash when it accidentally tries to
treat a remote directory like it is a remote directory.

[simojo]

Putting on hold for the Fall 2023 semester. This is not central to the project, and we already have remote config files, which is arguably the most important.