GeezerVison

Table::renameKeyInAllConstraints() looped over m_foreignKeys with
for(...; ++it) while the match_and_rename helper already advances the
iterator (it = container.erase(it)). After a rename the loop skipped the
next foreign key, leaving it on the old column name, and when the renamed
entry was the last one it incremented end(), which is undefined behaviour.

Let the helper advance the iterator, like the index constraint loop above.

Add tests for renaming keys in foreign keys and index constraints, and a
regression test for moving an AUTOINCREMENT primary key (sqlitebrowser#3953).

Likely fixes sqlitebrowser#3994

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>