AUTO: Sync ScalarDB docs in English to docs site repo (#1804)

Co-authored-by: josh-wong <joshua.wong@scalar-labs.com>

Author: github-actions[bot]

versioned_docs/version-3.15/scalardb-cluster/scalardb-abac-status-codes.mdx

@@ -381,6 +381,14 @@ The namespace policy for the policy and namespace already exists. Policy: %s; Na
 The table policy for the policy and table already exists. Policy: %s; Table: %s
 ```
 
+### `DB-ABAC-10045`
+
+**Message**
+
+```markdown
+The user does not exist. Username: %s
+```
+
 ## `DB-ABAC-2xxxx` status codes
 
 The following are status codes and messages for the concurrency error category.

versioned_docs/version-3.15/scalardb-core-status-codes.mdx

@@ -1407,6 +1407,230 @@ Missing required field or column mapping for partition key %s
 Missing field or column mapping for %s
 ```
 
+### `DB-CORE-10177`
+
+**Message**
+
+```markdown
+Something went wrong while converting the ScalarDB values to strings. The table metadata and Value datatype probably do not match. Details: %s
+```
+
+### `DB-CORE-10178`
+
+**Message**
+
+```markdown
+The provided file format is not supported : %s
+```
+
+### `DB-CORE-10179`
+
+**Message**
+
+```markdown
+Could not find the partition key
+```
+
+### `DB-CORE-10180`
+
+**Message**
+
+```markdown
+The source record needs to contain all fields if the UPSERT turns into an INSERT
+```
+
+### `DB-CORE-10181`
+
+**Message**
+
+```markdown
+Record already exists
+```
+
+### `DB-CORE-10182`
+
+**Message**
+
+```markdown
+Record was not found
+```
+
+### `DB-CORE-10183`
+
+**Message**
+
+```markdown
+Could not find the clustering key
+```
+
+### `DB-CORE-10184`
+
+**Message**
+
+```markdown
+No table metadata found
+```
+
+### `DB-CORE-10185`
+
+**Message**
+
+```markdown
+The data mapping source field '%s' for table '%s' is missing in the json data record
+```
+
+### `DB-CORE-10186`
+
+**Message**
+
+```markdown
+The CSV row: %s does not match header: %s.
+```
+
+### `DB-CORE-10187`
+
+**Message**
+
+```markdown
+Expected JSON file content to be an array
+```
+
+### `DB-CORE-10189`
+
+**Message**
+
+```markdown
+Missing option: either '--namespace' and'--table' or '--control-file' options must be specified.
+```
+
+### `DB-CORE-10190`
+
+**Message**
+
+```markdown
+The file '%s' specified by the argument '%s' does not exist.
+```
+
+### `DB-CORE-10191`
+
+**Message**
+
+```markdown
+Cannot write to the log directory: %s
+```
+
+### `DB-CORE-10192`
+
+**Message**
+
+```markdown
+Failed to create the log directory: %s
+```
+
+### `DB-CORE-10193`
+
+**Message**
+
+```markdown
+Failed to parse the control file: %s
+```
+
+### `DB-CORE-10194`
+
+**Message**
+
+```markdown
+No permission to create or write files in the directory: %s
+```
+
+### `DB-CORE-10195`
+
+**Message**
+
+```markdown
+Failed to create the directory: %s
+```
+
+### `DB-CORE-10196`
+
+**Message**
+
+```markdown
+Path exists but is not a directory: %s
+```
+
+### `DB-CORE-10197`
+
+**Message**
+
+```markdown
+File path must not be blank.
+```
+
+### `DB-CORE-10198`
+
+**Message**
+
+```markdown
+File not found: %s
+```
+
+### `DB-CORE-10199`
+
+**Message**
+
+```markdown
+Invalid date time value specified for column %s in table %s in namespace %s.
+```
+
+### `DB-CORE-10200`
+
+**Message**
+
+```markdown
+Key-value cannot be null or empty
+```
+
+### `DB-CORE-10201`
+
+**Message**
+
+```markdown
+Invalid key-value format: %s
+```
+
+### `DB-CORE-10202`
+
+**Message**
+
+```markdown
+Value must not be null
+```
+
+### `DB-CORE-10203`
+
+**Message**
+
+```markdown
+Delimiter must not be null
+```
+
+### `DB-CORE-10204`
+
+**Message**
+
+```markdown
+Config file path must not be blank
+```
+
+### `DB-CORE-10205`
+
+**Message**
+
+```markdown
+The namespace has non-ScalarDB tables and cannot be dropped. Namespace: %s; Tables in the namespace: %s
+```
+
 ## `DB-CORE-2xxxx` status codes
 
 The following are status codes and messages for the concurrency error category.
@@ -2015,6 +2239,46 @@ Something went wrong while trying to save the data. Details: %s
 Something went wrong while scanning. Are you sure you are running in the correct transaction mode? Details: %s
 ```
 
+### `DB-CORE-30049`
+
+**Message**
+
+```markdown
+Failed to read CSV file. Details: %s.
+```
+
+### `DB-CORE-30050`
+
+**Message**
+
+```markdown
+Failed to CSV read header line. Details: %s.
+```
+
+### `DB-CORE-30051`
+
+**Message**
+
+```markdown
+Data chunk processing was interrupted. Details: %s
+```
+
+### `DB-CORE-30052`
+
+**Message**
+
+```markdown
+Failed to read JSON file. Details: %s.
+```
+
+### `DB-CORE-30053`
+
+**Message**
+
+```markdown
+Failed to read JSON Lines file. Details: %s.
+```
+
 ## `DB-CORE-4xxxx` status codes
 
 The following are status codes and messages for the unknown transaction status error category.