installs would have had altered behavior with the FullControl auth
strategy, erroneous return while creating the default user, added help
file, added ability to skip first user or cancel the wizard altogether.

* create initial admin user with difficult password (based on UUID)
* force login with password as security token
* force initial admin user creation

[Fix JENKINS-33245] core asset artifacts bloated due to faulty build assembly step

More config tab tests (Jenkins 2.0)

 As well as finding in sections after adoption.

[FIXED JENKINS-23378] Servlet 3.1

Conflicts:
	test/pom.xml

Integrate newer version of test-harness

not just those who have one of the roles defined in this web.xml

The special role name $B!H(B*$B!I(B is a shorthand for all role names
defined in the deployment descriptor. The special role name $B!H(B**$B!I(B is a
shorthand for any authenticated user independent of role. When
the special role name $B!H(B**$B!I(B appears in an authorization constraint,
it indicates that any authenticated user, independent
of role, is authorized to perform the constrained requests.

Re-enable installer tests

Removes mention of http.proxyHost property

The root problem was missing <scope>test</scope> in domain-discovery.

Start declaring servlet 3.1 dependency

[JENKINS-33068] AsyncPeriodicWork/AsyncAperiodicWork log files rotation

Fix proxy server name documentation

Pull in new version of Stapler

[JENKINS-31152] Add Pipeline plugins, select by default

Adding a module to allow organizations to track usage of Jenkins within their domain