Include workaround for local deployment with different hostname

Certificate Hostname Issue:

When OpenCAPIF is deployed with the default hostname (capifcore), it functions correctly. However, if deployed with any other hostname (e.g., capif.xflow or lab-oai.etsi.org), the certificates are still generated with the default hostname (capifcore). This prevents successful requests using the certificates.

While we have identified a workaround, we believe a clear guide on generating certificates for custom hostnames would be beneficial for the community.

Workaround Steps:

Modify the hostname in the file capif/services/vault/vault_prepare_certs.sh on lines 43, 68, and 95.

Update the url parameter of the CCF from capifcore to the desired hostname in the file capif/services/register/config.yaml.