v3.0.0: remove gw2raidar support

This is a major release, as it's been some time since the last update.

BREAKING CHANGE

The major change in this release is that gw2raidar support has been entirely removed. The reasons for this are numerous.

• gw2raidar uploading is problematic, because the upload doesn't return a permalink immediately. Instead, there is a lot of futzing around with digging through their API and trying to correlate the links to the correct local boss files. This is fragile, and slow.
• gw2raidar devs haven't responded to my requests for a better API that allows me to request a permalink for a specific file I uploaded
• In my experience, their site has been slow, and difficult to use. Many users have told me that they do not enable gw2raidar uploads anymore. I have also stopped enabling it. This means that I'm likely to break the support as I continue to update and add new features.

If you are interested in the gw2raidar support, you're welcome to stick to the v2.5.0 release, or fork this project. If an active developer is willing to maintain the support in the current code, I'm willing to work with you, but I no longer have time to maintain the support given the above issues.

Highlights

This release also includes several other useful updates, including the following new features

• format-encounters learned to group bosses together by checking the time between them. Instead of just grouping all bosses on a single day, the script will keep a group of encounters together as long as there isn't a large gap where no boss was killed. This allows keeping consistent groupings together when publishing a set of encounters that crosses the date line. The groups will always keep raids, golem training encounters, and fractals separately. Additionally, encounters of separate guilds will not be grouped.
• format-encounters learned to optionally post a "total duration" of a set of grouped encounters. This duration includes possibly un-published failed encounters, and is the total time from the start of the first encounter in the set until the end of the last encounter. This data can be useful for showing approximately how long your group takes to clear that set of encounters.
• simpleArcParse gained support for outputting data in a simple JSON format, and is now the main format used by the other scripts. Note that the old keywords continue to work for backwards compatibility.
• you can now use an environment variable to modify what configuration file is loaded. This can be used to write wrapper scripts which run the upload and format using different configurations.
• simpleArcParse now can handle training golem encounters correctly

Changes since v2.5.0

• Mark Bandit Trio as a wing2 boss
• avoid storing the precise duration string if it's empty
• use the best available timestamp if there is no LOGEND event when calculating duration
• refactor how we split encounters into groups, to prepare for more robust grouping
• check for each dll when attempting to download the experimental ArcDPS versions
• remove the v1 to v2 configuration conversion script
• add vim modelines to the .ps1 files
• remove gw2raidar support entirely (see highlights above for more information)
• completely drop support for loading the old v1 configuration format
• combine commonConfigurationFields into the v2 configuration section
• Add a new "publish_encounters" option for guilds
• Add local start and end time extraction support in simpleArcParse
• improve logic for grouping encounters based on "time" (see highlights for details)
• add support for showing an estimate of the total time a block of encounters ran
• Avoid crashing if an encounter doesn't get recognized as belonging to any guild
• Add an environment variable to control what configuration file to load
• add training golem IDs to simpleArcParse
• log golem encounters separately from raids and fractals
• add a new JSON output format for simpleArcParse
• convert the upload and format scripts to use the JSON format.