Make controller compatible with express versions 4 and 5

[ushkarev]

• express 4’s router methods allow wildcard paths in the form '*'
• express 5’s router methods require wildcard placeholders in paths to be named, eg. '*allPaths'
• …and there is no wildcard syntax that is common to both. For example, express 4 treats '*allPaths' as requiring the text “allPaths” to appear in the URL path.

However, both allow specifying a RegExp object directly, thereby bypassing the use of differing versions of path-to-regexp (which are used under the hood on string paths).

This should address #208 but by different means.

[ushkarev]

I ran the tests locally against 4 and 5 and they both seem happy. I didn’t want to mess with your workflows so didn’t add anything to ci.yaml for testing against both versions.

What do you think about this approach? Alternatives I considered:

• discover the current express version and use different string constants (doesn’t work since version is not exposed anywhere in the express lib and reading package.json feels dirty)
• an express-5 branch but that would be a bit too messy and forking would lead to divergence
• trying '*' first, catching the appropriate error from path-to-regexp then retrying '*allPaths' (I figure this is a bit brittle, could catch the wrong error, could be a bit slow)

[ushkarev]

@cmcgee4801995 I notice you’ve made some recent commits to this repo… what do you think about this PR?