Multiple active keys when ovsx.integrity.key-pair=create with >1 server pod

[ErikaMolnar]

Hello,

Just wanted to report a behavior I've noticed.

With ovsx.integrity.key-pair=create and >1 server pod starting at once, both generate a key and mark it active in the database (a clean deployment all at once). Later, /api/-/publish generates the following error due to the two active keys:

IncorrectResultSizeDataAccessException: query did not return a unique result: 2

As a workaround, I disabled and left only one key active:

UPDATE signature_key_pair SET active = (id = some_id);

Would you consider making key creation idempotent and concurrency-safe?