Stop explicitly blocking Vanilla Method Profiler

At the time this was re-added, there was concern around how the JIT
would handle the system property that enabled it.

This shouldn't be a problem, and as such we no longer need to block
access to it.

The Vanilla Method Profiler will not provide much to most users however
there is no harm in providing it as an option. For most users, the
recommended and supported method for determining performance issues with
Paper will continue to be Timings.

Spigot-Server-Patches/0236-Include-Log4J2-SLF4J-implementation.patch

@@ -0,0 +1,26 @@
+From b810abd1c308634b722548b03cd532dba405ead6 Mon Sep 17 00:00:00 2001
+From: Minecrell <minecrell@minecrell.net>
+Date: Thu, 21 Sep 2017 16:33:35 +0200
+Subject: [PATCH] Include Log4J2 SLF4J implementation
+
+
+diff --git a/pom.xml b/pom.xml
+index 28976dae..ffa9f5a9 100644
+--- a/pom.xml
++++ b/pom.xml
+@@ -98,6 +98,12 @@
+         </dependency>
+ 
+         <!-- Paper - Add additional Log4J dependencies -->
++        <dependency>
++            <groupId>org.apache.logging.log4j</groupId>
++            <artifactId>log4j-slf4j-impl</artifactId>
++            <version>2.8.1</version>
++            <scope>runtime</scope>
++        </dependency>
+         <dependency>
+             <groupId>org.apache.logging.log4j</groupId>
+             <artifactId>log4j-iostreams</artifactId>
+-- 
+2.14.3
+