feat: Overseerr to Jellyseerr migration (#2019)

* feat: add Overseerr migration

* refactor: rename to Seerr

* refactor: more rename to Seerr

* feat: update the value of the MediaStatus.DELETED enum

* fix: add more details in migration logs

* fix: replace .update by .save for TypeORM hooks

* fix: add fake migration to skip the duplicated UpdateWebPush migration

* fix: rewrite the AddUserAvatarCacheFields migration for Overseerr merge

* fix: replace jellyseerr migrations with a dedicated one for overseerr

* fix: update overseerr migration

* fix: update overseerr migration

* fix: remove irrelevant changes

* fix: typos

* docs: update jsdoc comment

* docs: update seerr description

* docs: fix the contributing.md link

* fix: remove unwanterd change on postgres dev datasource

* docs: add latest tag to docker image

* fix: migrate old deleted status for 4k media

* fix: update Seerr version check

docs/using-seerr/notifications/webpush.md

@@ -0,0 +1,23 @@
+---
+title: Web Push
+description: Configure web push notifications for your users.
+sidebar_position: 2
+---
+
+# Web Push
+
+The web push notification agent enables you and your users to receive Seerr notifications in a supported browser.
+
+This notification agent does not require any configuration, but is not enabled in Seerr
+
+:::warning
+Web push notifications require a secure connection to your Seerr instance. Refer to the [Reverse Proxy](/extending-seerr/reverse-proxy) documentation for more information.
+:::
+
+To set up web push notifications, simply enable the agent in **Settings → Notifications → Web Push**. You and your users will then be prompted to allow notifications in your web browser.
+
+Users can opt out of these notifications, or customize the notification types they would like to subscribe to, in their user settings.
+
+:::info
+Web push notifications offer a native notification experience without the need to install an app.
+:::