Bundle pool + mutex fix

[dmarzzz]

📝 Summary

What

This PR has 2 main changes:

1. It moves all bundle related functions and data structures out of core/tx_pool.go into core/bundle_pool.go.
2. Uses a bundle specific mutex Does AddMevBundle need to use global pool mutex ? #7

Why

1. I personally find it easier to maintain forks by separating files, and it also allows us to test the bundle pool more easily. Happy to revert if theres good reason not to make this change!
2. The mutex used by the current bundle functionality in core/tx_pool.go is shared by other functions in the txpool. Depending on your mempool size this could cut locks considerably.

Testing

• Added a new test file for bundles
• Running this code on private network right now with no issues. That being said I will be doing more testing on a private network tomorrow to see if theres any noticeable performance difference.

📚 References

#7

• I have seen and agree to CONTRIBUTING.md

[dmarzzz]

just now seeing theres a build error, will check that out shortly

[dmarzzz]

hey @Ruteri , didn't have time to fix this test failure over the holidays but curious if y'all are interested in this PR? If not I can submit another w/ just the mutex change.

[Ruteri]

I'm, not sure if moving the txpool parts in the additional file won't be prone to later rebase issues and confusion

[Ruteri]

hey @Ruteri , didn't have time to fix this test failure over the holidays but curious if y'all are interested in this PR? If not I can submit another w/ just the mutex change.

I think the changes are worthwile, and if you fix the build issues we'll merge