Ensure unique entries in DamageState and DamageMethod tables

The tables DamageState and DamageMethod should not contain same entries twice. The best solution seems to be a table constraint.

The insert functions should also return the id of the entry, regardless of the entry being accepted or already present in the table. This will make the handling of damage data easier in the exposure-lib.