corba: fixed exception handling when sending oneway operations

Signed-off-by: Johannes Meyer <johannes@intermodalics.eu>
corba: added cmake cache variable PLUGINS_CORBA_SEND_ONEWAY_OPERATIONS to enable or disable oneway operations

If PLUGINS_CORBA_SEND_ONEWAY_OPERATIONS is set to ON, operations that have a collect arity of zero
(void return value and no reference arguments) are sent as oneway calls. The fake SendHandle returned to
the caller will always evaluate to SendSuccess, as if the operation would have been completed successfully.

Note that exceptions in the operation implementation are not forwarded to the caller and print a log message
at the server's side only.

Signed-off-by: Johannes Meyer <johannes@intermodalics.eu>
corba: added cmake cache variable PLUGINS_CORBA_PORTS_DISABLE_SIGNAL to disable remote signalling

If PLUGINS_CORBA_PORTS_DISABLE_SIGNAL is set to ON, writing into ports that are connected to a remote
port via the CORBA transport will not signal the remote side or trigger the owning TaskContext. The
remote side has to poll the port periodically.

Signalling is only active if pull is set to true in the ConnPolicy. Otherwise every write() is pushed
to the remote side and PLUGINS_CORBA_PORTS_DISABLE_SIGNAL has no effect.

Signed-off-by: Johannes Meyer <johannes@intermodalics.eu>
corba: added cmake cache variable PLUGINS_CORBA_NO_CHECK_OPERATIONS to disable operation signature checking

If PLUGINS_CORBA_NO_CHECK_OPERATIONS is set to ON, producing call and send handles for remote operations
will not check the argument types. Instead, calling or sending operations with an incompatible signature
will trigger an exception at runtime.

Signed-off-by: Johannes Meyer <johannes@intermodalics.eu>