Improve proof management

During the verification of a property, multiple kcfg files are produced. Comparing and inspecting back and forth such files is often part of the verification process. Here are some improvements that would reduce the friction of handling such files.

• Have kontrol foundry-show testProperty and kontrol foundry-view-kcfg testProperty default to the latest kcfg of testProperty. Currently, if there are multiple kcfgs for testProperty, an error is thrown asking for the desired id
• Have kontrol foundry-show and kontrol foundry-view-kcfg with no more arguments show all different proofs possible for display, so that the user can interactively pick one from the list
• Allow deletion of kcfgs from the cli tool, perhaps with a new command like kontrol foundry-manage-kcfg
• Add KEVM/Kontrol version to proofs as logging info, similarly as ids. Such information would be displayed with kontrol foundry-list, and could be included with foundry-show and foundry-kcfg
• Allow users to custom proof names. For instance, appending some string to Test.testProperty like Test.testProperty-ModificationA. This would allow for keeping better track of the particularities of each proof

Begin with the foundry-show, foundry-view-kcfg, foundry-list, and foundry-kcfg CLI entry points named in the issue, and trace how they select and display proofs. The issue contains five separate proposals, so first define which behavior is in scope and its acceptance criteria; done should be demonstrated for the selected proposal without leaving the others ambiguous.