Fix archive node block insertion failing when blocks are processed in parallel

When two blocks were inserted at the same time and shared data such as a zkApp command, a public key, or a token, the archive node could fail with a database uniqueness error and abandon the whole block. Inserts now let the database resolve these collisions, so concurrent block insertion succeeds.
