feat: permit default api context config to be used

[ndr-brt]

What this PR changes/adds

Remove the useDefaultContext attribute from WebServiceSettings, because it's use was not clear and it didn't permit runtimes to start with default configuration.

Why it does that

Briefly state why the change was necessary.

Further notes

• removed also name because it was used only for logging, and for that contextAlias can be used as well
• uniformed the defaultPath value in the form of /api/<context_alias>
• the current design of the definition and use of these configurations is not really lean and it could deserve some more love

Linked Issue(s)

Closes #4669

Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

[jimmarino]

Agreed that the current context configuration is not intuitive, particularly because it involved multiple objects. Having multiple objects under the hood is OK, but there should be an extension SPI that simplifies/hides their use.

[wolf4ood]

Yeah it's a bit convoluted and misleading on who actually adds the port mapping, that can happen in two places. Since now the pattern is to have always a module *ApiConfiguration that make usage of WebServiceSettings that handles the default values when not configured, I would propose to remove the auto-port mapping from config in the JettyConfiguration and always do this using WebServiceSettings with the WebServiceConfigurer