Avoid spamming conductor logs with object exceptions

Conductor's logs should include tracebacks only when something
unexpected happened, which is why we have the client_exceptions()
decorator. The object_action() and object_class_action() methods
are used for direct remoting of object methods, and thus really
should forward *any* exception to the client.

This patch does that, and also adds missing tests for these two
methods to verify the normal and exception-wrapped behavior.

Closes-bug: #1233789
Closes-bug: #1084706
Change-Id: I505462fa429a6aa68e7b8a08ec2b704bf18d029c
Open Icehouse development

This should be accepted/merged once all the RC1 bugfixes are in.

This bumps the target version to 2014.1, effectively opening the master
branch to Icehouse development, ending the feature freeze.

The Havana release branch is cut from the previous commit in master.

Change-Id: Ia3a41177e3c91bd75b38833761f9f8af2b503e4b
Merge "Open Icehouse development"
Merge "Avoid spamming conductor logs with object exceptions"