AEWeb uses full certification chain

### Is your feature request related to a problem?

A website deployed to AEWeb cannot provide its full SSL certification chain.
Because of that we usually provide the last chain part (certificate directly related to the domain name).

Some Webview implementations require the full cert chain (with intermediate certs) to perform the TLS handshake.

### Describe the solution you'd like

Add the management of full certs chain to aeweb.

- [ ] GitHub Action : handle full cert chain validation using [tls.createSecureContext](https://nodejs.org/api/tls.html#tlscreatesecurecontextoptions) `cert` array
- [ ] AENode : update cert/domain name matching

Start by tracing the AEWeb GitHub Action's certificate validation and the AENode certificate/domain-name matching path; review Node.js tls.createSecureContext and its cert-array behavior. Done means full certificate chains are handled in both listed areas and Webview TLS handshakes can use the intermediate certificates.

Written by the indexing model from the issue text.