Refactor SQL exception handling and config structure

Simplify SQL exception tracking by replacing error message mappings
with a list of relevant error numbers in appsettings.json. Remove
custom error message logic and related classes, introducing
SqlExceptionOptions to hold tracked error codes.

src/ReC.Application/Common/Options/SqlExceptionOptions.cs

@@ -0,0 +1,6 @@
+namespace ReC.Application.Common.Options;
+
+public class SqlExceptionOptions
+{
+    public HashSet<int> SqlExceptionNumber { get; set; } = [];
+}

src/ReC.Application/Common/Options/SqlExceptionTranslatorOptions.cs

@@ -1,24 +0,0 @@
-namespace ReC.Application.Common.Options;
-
-public class SqlExceptionTranslatorOptions
-{
-    public HashSet<int> ErrorNumbers { get; private set; } = [];
-
-    private Dictionary<int, string> _badRequestMessages = new()
-    {
-        [515] = "{Operation} '{Target}' failed because a required field was not provided or was null. Verify mandatory values and retry.",
-        [547] = "{Operation} '{Target}' failed because one or more referenced entities do not exist or violate relational rules. Please verify identifiers and constraints.",
-        [2601] = "{Operation} '{Target}' failed because the data conflicts with a unique constraint. Remove duplicate values and retry.",
-        [2627] = "{Operation} '{Target}' failed because the data conflicts with a unique constraint. Remove duplicate values and retry."
-    };
-
-    public Dictionary<int, string> ErrorMessages
-    {
-        get => _badRequestMessages;
-        set
-        {
-            _badRequestMessages = value;
-            ErrorNumbers = [.. value.Keys];
-        }
-    }
-}