Improvements to Kontrol UX

There are currently several possible ways to improve the UX of K Foundry:

• Fix broken Discord link in the output: https://github.com/runtimeverification/evm-semantics/blob/bc5943c7550787d1c01aa0b92f66c95d5f1baefe/kevm-pyk/src/kevm_pyk/utils.py#L179
• Make infinite_gas the default option — will be addressed in https://github.com/runtimeverification/kontrol/issues/38
• When showing the results for failed proofs, distinguish between different failure reasons and show it to the user (e.g., failed assert, failed require , intoverflow, etc.)
• Provide users with a flag that lets them specify which failure reasons they care about, i.e., whether we should look for all possible failures or just, e.g., failing asserts.
• Consider renaming variable names is the generated model/counterexample to match their Solidity counterparts (currently, the names of the environmental variables correspond to the EVM opcodes that is used to retrieve their values). E.g., consider renaming block.number to NUMBER_CELL, x toVV0_x_114b9705;
• Introduce different verbosity levels for foundry-kompile, foundry-prove (https://github.com/runtimeverification/evm-semantics/issues/1950)
• Make KEVMCheats a library — will be addressed in https://github.com/runtimeverification/kontrol/issues/11

The issue groups several unchecked ideas: failed-proof reporting, failure filters, generated-model naming, and verbosity for foundry-kompile and foundry-prove. Start by choosing one item and reading the referenced entry points or issues, including evm-semantics#1950; this issue is not specific enough to define a single done condition.