Signed-off-by: Joakim Erdfelt <joakim.erdfelt@gmail.com>

 + Created a common `Mapping` base for `FilterMapping` and `ServletMapping`
 + `Mapping` contains an array of PathSpec.  The `String` based methods assume `ServletPathSpec`.
 + Convert most handling of string pathSpecs to `PathSpec` instances
 + Modified `ConstraintMapping` to also use a PathSpec
 + Modified JSP and annotation handling to cope with any existing non standard path specs
 + Made ServletHandler update mappings respect the order of the mappings

 TODO:
 + Should `ConstraintMapping` extend `Mapping` ?
 + Convert `ConstraintSecurityHandler` to use `PathMappings` so it can handle non standard PathSpecs
 + Review remaining calls to `Mapping.getPathSpecs` and `ConstrainMapping.getPathSpec`
 + Currently Quick Start operates on just the string versions of PathSpec, as it must be able to write a web.xml which can only contain standard path specs.  Should it fail when it sees a non standard pathspec, or assume that it will again be programmatically added during quick start?
 + Review how frequently we are creating new arrays of path spec and/or converting path specs to/from strings.  Best resolution for such things are ultility methods on Mapping (eg `#containsPathSpec`)
 + More tests

 + Converted `ConstraintSecurityHandler` to use `PathMappings` so it can handle non standard PathSpecs

…port-alt

Signed-off-by: gregw <gregw@webtide.com>

 + Fixed test by reverting ServletMapping normalize

 + More tests

…10-bespoke-pathspec-support-alt

…port-alt

Signed-off-by: gregw <gregw@webtide.com>

Signed-off-by: gregw <gregw@webtide.com>