Standardise context id for web layer

Jakarta Authorization uses a context id to associate methods with a given app running on an application server.

For Jakarta Authentication, in the web layer, we have standardised such an ID. We should do the same for Jakarta Authorization (and use the same ID). As Enterprise Beans is effectively deprecated, we should leave the context ID for that as it's now, i.e. vendor specific.

As an example, in GlassFish the vendor specific context ID is now:

```java
// in webBundleDescriptor
getApplication().getRegistrationName()) +
'/' +
getApplication().isVirtual()?
getApplication().getRegistrationName() :
getModuleDescriptor().getArchiveUri();
```

The standard 'appContextId' used by Jakarta Authentication:

```java
servletContext.getVirtualServerName() +
" " +
servletContext.getContextPath();
```

Start by tracing the web-layer context ID from the mentioned webBundleDescriptor and servletContext entry points, comparing the GlassFish vendor-specific value with Jakarta Authentication's standard appContextId. Done means Jakarta Authorization uses the same standard web appContextId, while the Enterprise Beans context ID remains vendor-specific.

Written by the indexing model from the issue text.