Add a switch for investigating constraint violation and improve relative tip logs

[ArgonarioD]

Background

While Jimmer’s feature of investigating constraint violations greatly facilitates debugging and make functions like automatic retries in specific scenarios more easier to be implemented, it can impose unexpected and uncontrollable query loads on the database during large-scale data insertions. Therefore, I think this feature:

• should be user-controllable
• should be disabled by default

to minimize the risk of production incidents caused by unexpected query loads, and let users take the blame for them.

Additionally, Jimmer’s current behavior is inconsistent for databases that abort transactions upon errors (these databases do not investigate without an active transaction, while the others investigate constraint violations under any circumstances) and lacks notifications. Providing such notifications would enhance user-friendliness.

Modification

1. Add a Boolean property investigateConstraintViolationEnabled to SqlClient. When set to true, the investigation feature is enabled; when set to false, it is disabled. If set to null, it indicates that the setting is not explicitly configured (default is disabled).
2. Add the above property to the Spring Boot application properties.
3. When this feature is not enabled, do not set a savepoint or conduct an investigation; directly execute convertFinalException.
4. If the user has not explicitly set investigateConstraintViolationEnabled and a constraint violation exception occurs, issue a warning log prompting the user to explicitly set this value.
5. If the user enables this feature and is using a database that aborts transactions upon errors, and the transaction is not activated, issue a warning log prompting the user to activate a transaction.