Fix BrokerRunning for skipping tests

The regression after #1190

The `assumeNoException(e)` was missed in the `BrokerRunning`
when we don't have a locally ran RabbitMQ and no requirement.
With the `assumeNoException(e)` test are skipped with positive
outcome

**Cherry-pick to `2.2.x`**

# Conflicts:
#	spring-rabbit-junit/src/main/java/org/springframework/amqp/rabbit/junit/BrokerRunning.java

Author: artembilan

spring-rabbit-junit/src/main/java/org/springframework/amqp/rabbit/junit/BrokerRunning.java

@@ -17,6 +17,7 @@
 package org.springframework.amqp.rabbit.junit;
 
 import static org.junit.Assert.fail;
+import static org.junit.Assume.assumeNoException;
 
 import java.util.Map;
 
@@ -59,10 +60,10 @@
  *
  * @author Dave Syer
  * @author Gary Russell
+ * @author Artem Bilan
  *
  * @since 1.7
- * @see Assume
- * @see org.junit.internal.AssumptionViolatedException
+ *
  */
 public final class BrokerRunning extends TestWatcher {
 
@@ -127,7 +128,7 @@ public static BrokerRunning isBrokerAndManagementRunning() {
 	 * @return a new rule that assumes an existing broker with the management plugin with
 	 * the provided queues declared (and emptied if needed)..
 	 */
-	public static BrokerRunning isBrokerAndManagementRunningWithEmptyQueues(String...queues) {
+	public static BrokerRunning isBrokerAndManagementRunningWithEmptyQueues(String... queues) {
 		return new BrokerRunning(true, true, queues);
 	}
 
@@ -274,6 +275,9 @@ public Statement apply(Statement base, Description description) {
 			if (fatal()) {
 				fail("RabbitMQ Broker is required, but not available");
 			}
+			else {
+				assumeNoException(e);
+			}
 		}
 		return super.apply(base, description);
 	}