plugins can be properly controlled by per-project matrix security.

See issues like JENKINS-6888.

Conflicts:
	core/src/main/java/hudson/model/AbstractItem.java
	core/src/main/java/hudson/model/AbstractProject.java
	core/src/main/java/hudson/model/Descriptor.java
	core/src/main/java/hudson/model/Hudson.java
	core/src/main/java/hudson/tasks/BuildTrigger.java
	core/src/main/resources/hudson/model/View/newJob.jelly
	core/src/main/resources/hudson/model/View/sidepanel.jelly
	core/src/main/resources/hudson/views/Messages_ja.properties
	maven-plugin/src/main/java/hudson/maven/MavenBuild.java
	maven-plugin/src/main/java/hudson/maven/reporters/MavenArtifact.java
	maven-plugin/src/main/java/hudson/maven/reporters/MavenArtifactRecord.java

[JENKINS-8446] it's better to let those directories setting be a part of JENKINS_HOME rather than being independent configuration properties, since they aren't orthogonal.

Although there aren't any Jenkins packages deployed that use a launch daemon, soon there will be.
Let's make the preinstall capable of handling that already now.

Files under /Applications are usually owned by root and wheel, unless admin user has dragged it there. Jenkins is not an install-by-dragging kind of app.

The Jenkins launch daemon is configured "RunAtLoad", i.e. it runs immediately. No need to start it.

Updated Jenkins CLI Version Command Output

Added example to make jenkins listen to IPv4 only.

Fix: jenkins did not record test results generated by the GWT maven plugin