Support proof-of-stake in mev-inspect-py

[come-maiz]

No description provided.

[bertmiller]

So I think this actually isn't going to be useful. There's not much happening on Kiln, so there are no bots running and capturing MEV, and nothing will be picked up by mev-inspect-py.

If Uniswap or other DEXes deploy on KIln then it would be interesting to deploy mev-inpsect-py. But again, there would need to be arb bots in order for mev-inspect-py to pick anything up so that alone isn't enough.

[gheise]

I second this. On top of that, there is no difference in the Execution Layer that is present on Kiln specifically that is relevant to mev-inspect post-merge

[come-maiz]

Renaming this. The purpose was to check if there are any differences after the merge that require changes in mev-inspect-py. My intuition is that there are non, but I will leave this here any way.

I think when we implement #6 and #9 we will touch mev-inspect-py and confirm.