[EPIC] Upgrades to engine for a new Test Results website for Edison

[Badgerati]

One of the features of Edison is the ability to post test results to a URL.
It would be ideal if Edison was shipped with a website that could be hosted, and supported an endpoint we could post to by default.

I've had a few thoughts about this, and the website itself will be written in node.js - mostly because I hate ASP.NET, and so that the site can be containerised/run on any OS more easily.

For now, whilst I think a little more, this is an epic to cover all of the new features, enhancements and bugs to fix to prepare for the site:

• New UrlOutputType needed, rather than using file's OutputType #61: New UrlOutputType needed, rather than using file's OutputType
• When a test run starts, Edison should send a callout to tell the website a run has started #62: When a test run starts, Edison should send a callout to tell the website a run has started
• When a test run ends, Edison should send a callout to tell the website the run has ended - and why #63: When a test run ends, Edison should send a callout to tell the website the run has ended - and why
• Need a new TestRunName, which can be more informative than TestRunId #64: Need a new TestRunName, which can be more informative than TestRunId
• Need a new TestRunProject identifier for test results #65: Need a new TestRunProject identifier for test results
• Need a new TestRunEnvironment identifier for test results #66: Need a new TestRunEnvironment identifier for test results
• Callouts sent to a TestResultUrl/Slack/etc should be run in a separate thread #67: Callouts sent to a TestResultUrl/Slack/etc should be run in a separate thread

[Badgerati]

Documentation written, will be uploaded when v1.5.0 is released.

Merged in develop branch.