Document Seerr permissions change

Signed-off-by: Anvil5465 <119350594+Anvil5465@users.noreply.github.com>

community-containers/jellyseerr/readme.md

@@ -2,6 +2,7 @@
 This container bundles Seerr and auto-configures it for you.
 
 ### Notes
+- **Migration from Jellyseerr**: Jellyseer previously ran as the root user. With the change to Seerr, it now runs rootless, meaning that if you previously used Jellyseerr, Seerr will not be able to access the config files generated by the old Jellyseerr container. To migrate, execute the following steps: (1) stop all containers using the AIO Interface, (2) run `sudo docker run --rm -v /var/lib/docker/volumes/nextcloud_aio_jellyseerr:/data alpine chown -R 1000:1000 /data`
 - This container is only intended to be used inside home networks as it uses http for its management page by default.
 - After adding and starting the container, you can directly visit `http://ip.address.of.server:5055` and access your new Seerr instance, which can be used to manage Plex, Jellyfin, and Emby.
 - In order to access your Seerr outside the local network, you have to set up your own reverse proxy. You can set up a reverse proxy following [these instructions](https://github.com/nextcloud/all-in-one/blob/main/reverse-proxy.md) and [Seerr's reverse proxy documentation.](https://docs.seerr.dev/extending-Seerr/reverse-proxy), OR use the Caddy community container that will automatically configure requests.$NC_DOMAIN to redirect to your Seerr. Note that it is recommended to [enable CSRF protection in Seerr](https://docs.seerr.dev/using-Seerr/settings/general#enable-csrf-protection) for added security if you plan to use Seerr outside the local network, but make sure to read up on it and understand the caveats first.