Ban database refactor (#42495)

* Ban DB refactor seems to work at a basic level for PostgreSQL

* New ban creation API

Supports all the new functionality (multiple players/addresses/hwids/roles/rounds per ban).

* Make the migration irreversible

* Re-implement ban notifications

The server ID check is no longer done as admins may want to place bans spanning multiple rounds irrelevant of the source server.

* Fix some split query warnings

* Implement migration on SQLite

* More comments

* Remove required from ban reason

SS14.Admin changes would like this

* More missing AsSplitQuery() calls

* Fix missing ban type filter

* Fix old CreateServerBan API with permanent time

* Fix department and role ban commands with permanent time

* Re-add banhits navigation property

Dropped this on accident, SS14.Admin needs it.

* More ban API fixes.

* Don't fetch ban exemption info for role bans

Not relevant, reduces query performance

* Regenerate migrations

* Fix adminnotes command for players that never connected

Would blow up handling null player records. Not a new bug introduced by the refactor, but I ran into it.

* Great shame... I accidentally committed submodule update...

* Update GDPR scripts

* Fix sandbox violation

* Fix bans with duplicate info causing DB exceptions

Most notably happened with role bans, as multiple departments may include the same role.

Content.Shared.Database/Bans.cs

@@ -0,0 +1,33 @@
+namespace Content.Shared.Database;
+
+/// <summary>
+/// Types of bans that can be stored in the database.
+/// </summary>
+public enum BanType : byte
+{
+    /// <summary>
+    /// A ban from the entire server. If a player matches the ban info, they will be refused connection.
+    /// </summary>
+    Server,
+
+    /// <summary>
+    /// A ban from playing one or more roles.
+    /// </summary>
+    Role,
+}
+
+/// <summary>
+/// A single role for a database role ban.
+/// </summary>
+/// <param name="RoleType">The type of role being banned, e.g. <c>Job</c>.</param>
+/// <param name="RoleId">
+/// The ID of the role being banned. This is likely a prototype ID based on <paramref name="RoleType"/>.
+/// </param>
+[Serializable]
+public record struct BanRoleDef(string RoleType, string RoleId)
+{
+    public override string ToString()
+    {
+        return $"{RoleType}:{RoleId}";
+    }
+}