Change CORS config key from path-prefix to path-expr; method names also

[tjquinno]

Resolves #1767

The value is, in fact, used as a pattern (expression) and not a prefix.

Signed-off-by: tim.quinn@oracle.com tim.quinn@oracle.com

[tomas-langer]

LGTM

[tomas-langer]

A note for consistency - in Security, we have the following configuration:

security.web-server:
        paths:
            - path: "/noRoles"
              methods: ["get"]
            - path: "/user[/{*}]"
              methods: ["get"]
              roles-allowed: ["user"]

I use just path, even though it can be an expression (as in the example above).
I did not feel the expr was required here.
In routing, we call it pathPattern

This is adding a third option.
Please consider this - does it make sense to change all of them to expression, or use one of the existing terms?

Options:

1. path
2. path-pattern
3. path-expr

I have approved this PR, as we may delay that decision for a future Helidon version...

[tjquinno]

After a quick slack chat with Tomas, I am re-changing the config key name to path-pattern and associated method names, arguments, etc. to pathPattern to be consistent with similar usage elsewhere in WebServer. Update to the PR coming soon.

[tomas-langer]

I like this!