implement server side default URI matching

[matlink]

See item 4 of #432

Watch #432 (comment) for a little different workflow

[BlackDex]

This still doesn't resolve the issue @dani-garcia mentioned in #432 (comment)

If you override this, and someone edit's that cipher, it will store the overridden value, and from that point on, it will not be the server side default anymore. If then at a later point you want to change the server-side default, all those previous values will never be updated to the new setting configured on the server side.

I think this will only cause confusion or maybe even issues.
Also, this also breaks the client side default uri match detection which they can configure them self.

[BlackDex]

From my point of view i still think this will cause more issues then it might solve for some people.
It is also error prone during handling or when you want to change the default to something else.

Going to close this one. If you think it still should be applied, please provide more detailed information or workflows on how this can work and ill recheck,