feat(forge): prompt address and uint cheatcodes

[kamuik16]

Closes #5509

cc @mattsse

In case of parse failure, it fails with these errors:

[FAIL. Reason: failed parsing "0x3C44CdDdB6a900fa2b585dd299e03d12FA4293B" as type `address`: parser error:
0x3C44CdDdB6a900fa2b585dd299e03d12FA4293B
^
Odd number of digits] testPrompt_Address() (gas: 2948)

[FAIL. Reason: failed parsing "-1" as type `uint256`: parser error:
-1
^
expected at least one digit] testPrompt_Uint() (gas: 3008)

[DaniPopes]

I'm not sure about this, since these are just vm.parse<Type>(vm.prompt()) users can do this in "userland", rather than keep bloating the already massive list of cheatcodes we have.

cc @mattsse @mds1 @klkvr

[Evalir]

some feedback on tests, and lets check in on @mds1 if this is what we actually want:

[mattsse]

I think the most common prompts will be address and uint, so having a builtin for these makes sense imo

[mds1]

One argument in favor of native cheats here is better UX. If I do vm.parseAddress(vm.prompt()) and the user leaves a character off the address, the script would revert when parsing fails, and now you have to start over. But if I do vm.promptAddress() I'd expect the TUI to say "invalid address" and let you try again without starting over