migrate Prover functionality from core repo

[ChaoticWalrus]

had to modify some paths / folder structure / etc

Marking this PR as a draft for the moment, as it's currently having compiler issues due to duplicate instances of IPauserRegistry.sol.

[stevennevins]

@ChaoticWalrus is this good to move out of draft status?

[ChaoticWalrus]

@ChaoticWalrus is this good to move out of draft status?

I marked it as a draft since it wasn't compiling / I didn't want to add to the list of these things to sort out. I'll take 15min and see if I can get it to run now after pulling from master.

[ChaoticWalrus]

hmm, @stevennevins I'm happy to have you take a look but am still struggling here.
The compiler doesn't seem to be playing nicely with the file/import structure (see https://github.com/Layr-Labs/eigenlayer-middleware/actions/runs/6591010121/job/17908751745?pr=4#step:9:24) -- feeling like this could maybe be a remappings issue but I didn't have any luck solving this locally

[stevennevins]

Looks like a remapping issue. Adding a remappings.txt or a remappings list in the foundry.toml might resolve

[stevennevins]

should this be empty?

[stevennevins]

I noticed in the action trace you shared this command wasn't found

[stevennevins]

Looks like a remapping issue. Adding a remappings.txt or a remappings list in the foundry.toml might resolve

It's probably not remapping-related now that I took more of a look. There might be some setup piece that isn't correct or path in the config that isn't correct with the slightly different directory structure

[ChaoticWalrus]

Looks like a remapping issue. Adding a remappings.txt or a remappings list in the foundry.toml might resolve

It's probably not remapping-related now that I took more of a look. There might be some setup piece that isn't correct or path in the config that isn't correct with the slightly different directory structure

Yeah, my bad, scripts need to also list the remappings and I missed one for 'eigenlayer-contracts'. CI should be running now but it's possible the rule still fails -- we'll see!

[ChaoticWalrus]

So this is now running as well as it was in the other repo.
The existing rules are failing, but due to 'havoc' behavior which really shouldn't be present, given the dispatching behavior defined in the spec.
We can merge this but it'll result in a failing CI for the moment, so... I'm fine either way 🤷

[ChaoticWalrus]

closing this PR as stale; if these rules are added, it should be in a new PR