if ingress tls is enabled, then adjust the config file to overwriteprotocol https as needed so reverse proxy works

Description of the change

Whatever changes are needed to config file to make a reverse proxy work should happen automatically if an ingress is enabled with tls.

Benefits

Folks deploying via helm chart should not have to know that they need to add a config section to get their reverse-proxy to work. It should be enough that they enabled an ingress with tls.

Possible drawbacks

None

Additional information

I had to add the following config to get the reverse-proxy to work, but every one deploying shouldn't have to dig this up every time, it should just be added automatically if an ingress was enabled with tls.

  nextcloud:

    # this is required or the reverse-proxy w/ ingress won't work
    configs:
      custom.config.php: |
        <?php
        $CONFIG = array (
          'overwriteprotocol' => 'https',
          'filelocking.enabled' => 'true',
          'enable_previews' => true,
        );

Since I'm not an expert I don't know if this config file overwrites default settings that I might actually need, or if it just appends these to an existing configuration. By just taking care of things for me, in response to enabling an ingress with tls, things will just work by folks who know the details and just take care of what needs to be taken care of automatically.

The issue names Helm ingress with TLS and the custom.config.php configuration, but gives no repository path or test. Start by locating the chart's ingress and Nextcloud configuration entry points, then verify that enabling ingress TLS makes reverse-proxy requests work without manually adding the shown configuration.