Ensure to match against the most specific route

[agubler]

Type: feature/bug

The following has been addressed in the PR:

• There is a related issue
• All code has been formatted with prettier as per the readme code style guidelines
• Unit or Functional tests are included in the PR

Description:

For routing the first match route specified in the configuration will be considered "the one", even if there is a more exact match in a later route within the configuration.

Assuming a routing configuration:

const config = [
    {
        path: 'foo',
        outlet: 'foo-one'
    },
    {
        path: 'foo',
        outlet: 'foo-two',
        children: [
            {
                path: 'baz',
                outlet: 'baz'
            }
        ]
    },
    {
        path: '{bar}',
        outlet: 'param'
    },
    {
        path: 'bar',
        outlet: 'bar'
    }
];

Current Behaviour

Routing to /bar, should match against the bar outlet as it's more specific (a string literal match) but currently would match against the param outlet because it is registered first.

Routing to /foo/baz would currently match against the outlet, foo-one with a type of partial, rather then correctly matching against the more exact outlet match baz.

Updated Bahaviour

Routing to /bar, will match against the bar outlet as it's more specific (a string literal match).

Routing to /foo/baz will match against outlet baz.

Resolves #83

[rorticus]

Might want to create constants for these numbers so we know what they mean!

[JamesLMilner]

These numbers look fairly arbitrary at first glance. Perhaps a comment to clarify?

[agubler]

They actually are fairly arbitrary, I went for a score that meant we could introduce other types of segments in the future (like maybe wild card, which would have an even smaller score).