Add cheatcodes that generate symbolic variables with custom names

[anvacaru]

Using custom_step to rename symbolic variables generated by cheatcodes.
Blocked on : runtimeverification/kontrol-cheatcodes#16

In this PR:

1. Adding a new #rename rule that all cheatcodes that generate symbolic variables would rewrite into.

    syntax RenameTarget ::= Int | Bytes | Map
    syntax KItem ::= #rename ( RenameTarget , String ) [symbol(foundry_rename)]
 // ---------------------------------------------------------------------------
    rule [rename]: <k> #rename(_,_) => .K ... </k>

The goal is to have a single cut-rule rename.
2. In KontrolSemantics, we add:

• _check_rename_pattern(self, cterm: CTerm) -> bool:
  • checks if the #rename cut-rule is at the top of the K Cell.
• _exec_rename_custom_step(self, cterm: CTerm) -> KCFGExtendResult | None:
  • takes the newly generated symbolic variable (target_var) and new name (new_name) from the top of the K Rule.
  • ensures that the new name is unique in the CTerm, if not, it appends an indexed suffix.
  • using Subst replaces all instances of the target_var with a new KVariable(new_name.token, target_var.sort) in the given CTerm configuration and constraints.

3. Added new unit and show integration tests.
4. Bumping kontrol-cheatcodes and forge-std versions for tests/integration/test-data/foundry

[palinatolmach]

lgtm!

[PetarMax]

Slightly late to the party - it would be great if we could make a minor adjustment where the indices are not separated from the name, like the backend has been doing for a while now - X, X0, X1, etc.