fix: EXPOSED-713 Allow entity batchInsert() to generate SQL for column values that match the default

[Avi18971911]

Description

Summary of the change: Changed the new function for Entities under EntityClass to explicitly insert default values (when provided for columns that have default values) even when an ID is provided. This should not have any impact other than the generated SQL explicitly including columns with default values if they are specified.

Detailed description:

• What: Entity insertion via new will generate SQL that will explicitly insert columns whose values match their default value.
• Why: To align the DAO SQL generation with the DSL, which will explicitly insert columns whose values match their default value.
• How: Removed an if statement that prevented explicit insertion if an ID was provided to the new() function

---

Type of Change

Please mark the relevant options with an "X":

• Bug fix
• New feature
• Documentation update

Updates/remove existing public API methods:

• Is breaking change

Affected databases:

• MariaDB
• Mysql5
• Mysql8
• Oracle
• Postgres
• SqlServer
• H2
• SQLite

Checklist

• Unit tests are in place
• The build is green (including the Detekt check)
• All public methods affected by my PR has up to date API docs
• Documentation for my change is up to date

---

Related Issues

[Avi18971911]

Removed this because it seemed redundant and prevented the explicit SQL generation. If there is an ID provided, it will always write the column value to writeValues in _writeIdColumnValue_, thus the check col !in writeValues will pick it up. That being said, might be missing something here. This change doesn't affect Composite IDs because _value is correspondingly set to null after _writeIdColumnValue_

[Avi18971911]

This seems like it may invoke a race condition, because if inserts gets cleared before this assertion passes, I think writeValues becomes empty.