Add autoconfig from MR96

- In your `docker-compose.yml` file update the following:

  - Set the nextcloud image to `registry.gitlab.e.foundation/e/infra/ecloud/nextcloud/selfhost:26-0-8`

  - Set the mailserver image to `mailserver2/mailserver:1.1.15`

  - In the `nginx:` service, `depends_on:` section, replace `- automx` with `- mail-autodiscover-autoconfig`

  - In the `mailserver:` service, `ports:` section, enable port 465 (remove the `#` at beginning)

  - Replace the whole `automx:` service with:

```

  mail-autodiscover-autoconfig:

    image: wdes/mail-autodiscover-autoconfig:latest

    container_name: mail-autodiscover-autoconfig

    restart: always

    networks:

      - default

    environment:

        ROCKET_PROFILE: production

        ROCKET_ADDRESS: "0.0.0.0"

        ROCKET_PORT: "80"

        APPLE_MAIL_UUID: ${AUTODISCOVER_AM_UUID}

        APPLE_PROFILE_UUID: ${AUTODISCOVER_AP_UUID}

        IMAP_HOSTNAME: ${SMTP_HOST}

        POP_HOSTNAME: ${SMTP_HOST}

        SMTP_HOSTNAME: ${SMTP_HOST}

```

- In your `config/nginx/sites-enabled/nextcloud.conf` change the following:

- Run:

  - `. scripts/base.sh`

  - `echo "AUTODISCOVER_AM_UUID=$(cat /proc/sys/kernel/random/uuid)" >> "$ENVFILE"`

  - `echo "AUTODISCOVER_AP_UUID=$(cat /proc/sys/kernel/random/uuid)" >> "$ENVFILE"`

  - `rm -rf config/automx/`

- In your `config/nginx/sites-enabled/nextcloud.conf` file change the following:

  - replace all occurences of `oc[ms]-provider` with `ocs-provider` (2 occurences, lines 83 & 98) (reference: https://github.com/nextcloud/server/issues/40803#issuecomment-1751717926)

- In your `config/nginx/sites-enabled/autoconfig.$DOMAIN.conf` and `config/nginx/sites-enabled/autodiscover.$DOMAIN.conf` files change the following:

  - replace `proxy_pass http://automx:80;` with `proxy_pass http://mail-autodiscover-autoconfig:80;`

- Run `docker-compose pull`

- If pulls are OK, run `docker-compose up -d`

  - `docker exec -u www-data nextcloud /var/www/html/occ config:system:set main_domain`

- Check all settings subsections starting from `/settings/admin/overview` while logged in with the admin user account to identify any issues found post upgrade

- Examine Docker situation with `docker ps` and `docker images`

  - If everything is OK (all needed containers running), you can cleanup with `docker system prune -a`