Remove unnecessary parameter in Configuration methods

[DasSkelett]

defaultRepo

Configuration.LoadOrCreateConfiguration() gets passed a defaultRepo parameter.
This is a relic of the early days of CKAN it seems, when the repositories were saved in the GUI configuration, but this got moved to the registry in 536637f.
Since then the parameter sits there unused.

path

Also SaveConfiguration() gets passed a path parameter, which is redundant since there is a specific path variable in the Configuration class. It's a bit dangerous too, because it could lead to a difference between the real save path and the one set in the configuration.
Now SaveConfiguration() takes the value out of the according object of Configuration, which happened in Save() before.

Add SpaceAfterMethodCallName to code formatting guideline

I added $2.SpaceAfterMethodCallName = False to the solution file, because MonoDevelop always inserted a space between method calls an round brackets.
Don't know if Visual Studio is okay with this, but I think in the worst case VS auto-removes the line again.
I encountered a strange Github display bug with the indentation in CKAN.sln, hence the 2 additional commits.

[DasSkelett]

As I wrote this PR I was wondering if SaveConfiguration() shouldn't be private instead of public, this would force Save() to be called from outside, which I understood is the goal of having this separate function.

[HebaruSan]

My rule of thumb: If you can make something private without breaking anything, do it.

[DasSkelett]

That's a great rule of thumb :P

[DasSkelett]

Okay, made it private, also LoadConfiguration() (because we have LoadOrCreateConfiguration()). This needed changing two tests to call LoadOrCreateConfiguration() instead of LoadConfiguration(), but that doesn't affect their result.

[DasSkelett]

That build fail was not my fault!

[HebaruSan]

Build fail? What build fail? 😉