SIARD Validation gets confused when two tables in different schemas have the same name.

[stighemmer]

Description: When multiple schemas exist, and two tables in different schema have the same name, the primary/candidate key part of SIARD validation gets confused and gives errors.

This example SIARD file is produced by dbptk itself.

Steps required to reproduce the bug:

1. Rename the attached testdb.zip to testdb.siard. testdb.zip

2. Validate it.

3. Read report. dbptk-validation-reporter-testdb-20240524221110141.txt Highlights:

A_M_5.8-1-2: [ERROR] : Primary key column reference id not found on dbo.testtable
A_M_5.11-1-2: [ERROR] : Candidate key column reference id not found on dbo.testtable

5. Notice that dbo.testtable does in fact have a column id.
6. But other.testtable do not.

Attach the dbptk-app.log.txt file below. dbptk-app.log.txt This log describes both the creation of the SIARD file and the validation of it.