Ensure errors on reote triggering get logged

If an error occurs while triggering a build the log message gets swallowed up and is not logged.

Instead I see this;

2011-02-01 15:36:58,489 INFO [2054569821@qtp-536836638-0] [AccessLogFilter] admin http://localhost:8085/api/rest/updateAndBuild.action?auth=4h02UJgOrr&buildKey=TEST-TDD 88101kb
2011-02-01 15:36:58,492 WARN [2054569821@qtp-536836638-0] [DefaultActionInvocation] No result defined for action com.atlassian.bamboo.v2.ww2.build.TriggerRemoteBuild and result input

Additionally we need to make it clear that plan is not being built because there weren't any changes detected since the last build.

I have run into this issue a few times in Support tickets with evaluators not being able trigger builds for the first time.