Krakenw warns about difference between .kraken.lock and .kraken.py when default interpreter_constraint is different because of different krakenw versions

[NiklasRosenstein]

If you use an older krakenw version which has as a default interpreter_constraint = >=3.10,3.11 to create a lock file and then upgrade krakenw to the latest version (which has the default interpreter_constraint = >=3.10), krakenw will report that the .kraken.lock and is out of sync with the .kraken.py, even though that's not entirely true.

[06/12/24 13:58:25] WARNING  Lock file ".kraken.lock" is outdated compared to requirements in ".kraken.py". Consider updating the lock file with "krakenw --upgrade lock"