[WFLY-1059] Add color-map attribute for pattern formatters

[jamezp]

So the subject doesn't say it all :)

First Commit (be8b31b)

The first commit is just to help tame the beast that is the logging subsystem configuration parser.

Second Commit (2c63cba)

The second commit just bumps the logging schema and model to 2.0.0.

Third Commit (f759306)

The third commit may or may not really be needed. At this point it's more of a place holder once 2.0 transformers are written.

Final Commit: (c803afa)

The final commit is the actual commit for the JIRA. This adds a new root resource called formatter. The only current formatter is the pattern-formatter, but there is a JIRA to allow for custom formatters which this change makes easier to implement.

I've also added a new attribute to most handlers called named-formatter. This attribute allows the new formatter resource to be defined for the handler. The original formatter attribute on the handler will continue to work in the same way it always has and will be the default when adding a handler.

There are currently no transformers for 2.0 -> 1.2, but there is WFLY-1807 to remedy that.

[wildfly-ci]

Build 313 is now running using a merge of c803afa925c4875b1a8d459c57dece48cff25736

[ctomc]

what is this used for?

[jamezp]

I was a bit iffy on it, but I was using it for undefining either the named-formatter if the formatter was explicitly set or the other way around. using `new ModelNode()`` might be a better solution though.

[ctomc]

or doing .clear() :)

[wildfly-ci]

Build 313 outcome was SUCCESS using a merge of c803afa925c4875b1a8d459c57dece48cff25736
Summary: Tests passed: 4004, ignored: 89 Build time: 1:26:16

[wildfly-ci]

Build 319 is now running using a merge of 5c4055eb2d7a26e0d5ece16c2772bfa87da38b98

[wildfly-ci]

Build 319 outcome was FAILURE using a merge of 5c4055eb2d7a26e0d5ece16c2772bfa87da38b98
Summary: Tests failed: 2 (2 new), passed: 4002, ignored: 89 Build time: 1:25:41

Failed tests

org.jboss.as.test.integration.ejb.timerservice.persistence.TimerServicePersistenceFirstTestCase.createAndCancelTimerService: java.lang.AssertionError
    at org.junit.Assert.fail(Assert.java:86)
    at org.junit.Assert.assertTrue(Assert.java:41)

org.jboss.as.test.integration.ejb.timerservice.persistence.TimerServicePersistenceSecondTestCase.testTimerServiceNotCalled: java.lang.AssertionError
    at org.junit.Assert.fail(Assert.java:86)
    at org.junit.Assert.assertTrue(Assert.java:41)

[jamezp]

This failure is unrelated, retest this please

[wildfly-ci]

Build 327 is now running using a merge of 5c4055eb2d7a26e0d5ece16c2772bfa87da38b98

[wildfly-ci]

Build 327 outcome was FAILURE using a merge of 5c4055eb2d7a26e0d5ece16c2772bfa87da38b98
Summary: Tests passed: 3811, ignored: 86; exit code 1 (new) Build time: 1:50:46

[jamezp]

retest this please

[wildfly-ci]

Build 330 is now running using a merge of 5c4055eb2d7a26e0d5ece16c2772bfa87da38b98

[wildfly-ci]

Build 330 outcome was SUCCESS using a merge of 5c4055eb2d7a26e0d5ece16c2772bfa87da38b98
Summary: Tests passed: 4002, ignored: 89 Build time: 1:26:11

[n1hility]

nifty

[ctomc]

this looks ok. @jamezp can you just rebase it to make sure, given some big changes ware merged recently.

[wildfly-ci]

Build 396 is now running using a merge of 20fee94

[jamezp]

Rebased. Just a side note if anyone has an argument against not changing the default logging.properties and subsystem to use the new pattern-formatter, I have no strong opinion either way.

[wildfly-ci]

Build 396 outcome was SUCCESS using a merge of 20fee94
Summary: Tests passed: 4344, ignored: 82 Build time: 1:29:49

[n1hility]

merged