feat(cheatcodes): support native `bound` cheatcode

[grandizzy]

Component

Forge

Describe the feature you would like

see convo foundry-rs/forge-std#584 (comment)

Additional context

• The uint and int strategies should take an option with min / max bound values
  

  foundry/crates/evm/fuzz/src/strategies/uint.rs

  Lines 96 to 109 in 2b39094

  	impl UintStrategy {
  	/// Create a new strategy.
  	/// #Arguments
  	/// * `bits` - Size of uint in bits
  	/// * `fixtures` - A set of fixed values to be generated (according to fixtures weight)
  	pub fn new(bits: usize, fixtures: Option<&[DynSolValue]>) -> Self {
  	Self {
  	bits,
  	fixtures: Vec::from(fixtures.unwrap_or_default()),
  	edge_weight: 10usize,
  	fixtures_weight: 40usize,
  	random_weight: 50usize,
  	}
  	}

  
  which should be enforced on value tree current values
  

  foundry/crates/evm/fuzz/src/strategies/uint.rs

  Lines 46 to 48 in 2b39094

  	fn current(&self) -> Self::Value {
  	self.curr
  	}

• the randomUint/randomInt cheatcodes should reuse the UintStrategy/IntStrategy to apply bounds (PR feat(cheatcodes): random* cheatcodes to aid in symbolic testing #8882 is updating these cheatcodes to use proptest strategies)

• for fuzzed tests we could use the inline config as suggested in feat: add boundLog to enable log-uniform sampling forge-std#584 (comment)

/// forge-config: default.fuzz.range.y = [1, 10];
function testFoo(uint256 x, uint256 y) public {

and pass the min / max bound values to UintStrategy/IntStrategy

• tests should make sure that, if fuzzing over a large space, logarithmic uniformity is preferred, whereas if fuzzing a uint8 then standard uniform sampling is preferred

[07Vaishnavi-Singh]

Hey I am working under WIEP (cohort 2 )and would like to work on this issue
I have understood the issue and maths involved in it
Would be great if u can assign me this issue :)
@zerosnacks @grandizzy

[07Vaishnavi-Singh]

Hey @zerosnacks , following the Contribution Guidlines when I am running cargo test --all --all-features there are 9 test cases failling in the original repo I forked and cloned n there are no additional test cases failling after adding boundLog that is required in this issue. Is there a problem in my project setting due to any dependency issue or should I just ignore these 9 failing test cases and make sure no additional test cases fail after adding the featire due to the newly added boundLog.
In case of incorrect project setup can you pls help to fix it.

[07Vaishnavi-Singh]

Hey, I got clarified about the above issue in the TG grp and run it locally for any additional Failing Testcases and the PR is ready to be reviewed.
Would be great if u can share your TG or X handle as that would help me close this issue earlier.

Thanks @grandizzy @zerosnacks

[malik672]

can I get assigned to this @jenpaff