Report the duplicate tileid when failing to insert data to collection

[Bang Pham Huu]

The error message should show the duplicate tileid when it has this problem which cannot insert data to a collection.

 [INFO] - 2019-08-22 16:00:07,855: Request: 'CREATE COLLECTION Global_Sentinel2_L1C_TCI_4 Global_Sentinel2_L1C_TCI_Set'... parsing... checking semantics... evaluating... ok
 [INFO] - 2019-08-22 16:00:08,043: Request: 'INSERT INTO Global_Sentinel2_L1C_TCI_4 VALUES <[0:0,0:0,0:0] {0c,0c,0c}> TILING ALIGNED [0:0,0:5999,0:5999] tile size 72000000'... parsing... checking semantics... evaluating... result type 'set<long>', 1 element(s)... [ERROR] - 2019-08-22 16:00:08,055, tile with id 271403 already exists.
[ERROR] - 2019-08-22 16:00:08,055, Commit failed: Base DBMS error 1: a tile with the same id already exists in the database; see the server log for more details.; aborting transaction.
 [INFO] - 2019-08-22 16:00:08,089: Request: 'commit TA'...

 Error: Base DBMS error 1: a tile with the same id 
already exists in the database; see the server log for more details

[Dimitar Misev]

It's reported in the log file; to a standard user it doesn't mean much at all that the tile id will be present in the client error message.

[Peter Baumann]

if it is in the log then it's ok.