* hacked together load balancing reroutes in fileconfig
* some renaming and refactoring
* more renames
* hacked away the old config json
* test for issue 213
* renamed key
* dont share ports
* oops
* updated docs
* mvoed docs around
* port being used
* hacking around to work out why logging and request id isnt working
* pass request id into logger so it can be structured, removed a bunch of debug logging we dont need because diagnostic trace gets it
* changed config dependency
* always have tracing available
* made it so we dont need to pass config into services.AddOcelot anymore with .net core 2.0
* add test
* lots of changes relating to logging and request ids, also updated documentation
* fixed failing test i missed
* brought in rafty
* moved raft classes into Ocelot and deleted from int project
* started to set up rafty in Ocelot
* RAFTY INSIDE OCELOT...WOOT
* more work adding rafty...just need to get auth working now
* rudimentary authenticated raft requests working
* asyn await stuff
* hacked rafty into the fileconfigurationcontroller...everything seems to be working roughly but I have a lot of refactoring to do
* updated to latest rafty that doesnt need an id
* hacky but all tests passing
* changed admin area set up to use builder not configuration.json, changed admin area auth to use client credentials
* missing code coverage
* ignore raft sectionf for code coverage
* ignore raft sectionf for code coverage
* back to normal filters
* try exclude attr
* missed these
* moved client secret to builder for authentication and updated docs
* lock to try and fix error accessing identity server created temprsa file on build server
* updated postman scripts and changed Ocelot to not always use type handling as this looked crap when manually accessing the configuration endpoint
* added rafty docs
* changes I missed
* added serialisation code we need for rafty to process commands when they proxy to leader
* moved controllers into their feature slices
