This is currently breaking the wiredtiger-compat-develop test.

As per the commit https://github.com/wiredtiger/wiredtiger/commit/f0138353697d8706bd1f26e83b9fff8f4e83af8d we will re-create the basecfg file when we open a connection, when one does not exist.

In the compat-develop test we are deleting the basecfg file initially and then running verify with the 2 older versions of the wt utility. The first call creates the basecfg file, which causes the second version to fail.

Should we look to stop the creation of basecfg when none exists and we are opening from the wt utility?