Adding stack trace as message in server's exception reply
Fixed build + changed advancedbus to accept string queueName, since it creates the queue (following the convention)
Using task continuation to handle all computation. So we are guaranteed proper error handling
Move+rename FreshQueue rpc strategies

Conflicts:
	Source/EasyNetQ/Rpc/FreshQueue/FreshQueueRpcFactory.cs
Created all reuseQueue files
pushed classes public so they can be manually chosen in the ioc container
Realized that only the client side is really aware of the difference between reuse and fresh queue strategy..
Andalso the impl of IRpc need not worry about it

Conflicts:
	Source/EasyNetQ/Rpc/AdvancedServerRpc.cs
	Source/EasyNetQ/Rpc/FreshQueue/FreshQueueServerRpc.cs
	Source/EasyNetQ/Rpc/IAdvancedServerRpc.cs
Added stacktrace in server's exception reply

Conflicts:
	Source/EasyNetQ/Rpc/FreshQueue/FreshQueueServerRpc.cs
Moved common rpc code to helper class
rename
Used Task-continuation monad for whole pipe line in the rpc-server. Then all errors (including unexpected ones) will be propagated to outer handler
wrapped advancedrpc.respond in proper task--continuations. To make sure that the error handler is always executed properly

Conflicts:
	Source/EasyNetQ/Rpc/AdvancedRpc.cs
rebased to new rpc pull request
cs proj missing in last commit
I felt a slight deja vu when I did these things the second time :-)
Merge branch 'single-queue-rpc' of https://github.com/tordenhunden/EasyNetQ into single-queue-rpc

Conflicts:
	Source/EasyNetQ/IAdvancedBus.cs
	Source/EasyNetQ/Rpc/AdvancedServerRpc.cs
	Source/EasyNetQ/Rpc/ReuseQueue/ReuseQueueAdvancedRpcFactory.cs