refactor: remove unused method

[dinhani-cw]

No description provided.

[github-actions]

PR Review 🔍

⏱️ Estimated effort to review [1-5]	2, because the PR involves removing unused code which is generally straightforward. However, understanding the context and implications of the removed code requires some domain knowledge about the system.
🧪 Relevant tests	No
⚡ Possible issues	Possible Bug: Removing the check_conflicts method and its related types (ExecutionConflicts, ExecutionConflictsBuilder) might impact other parts of the system if these components are used elsewhere indirectly or are planned to be used in future implementations. It's crucial to ensure that this method and its types are indeed not used anywhere else in the project.
🔒 Security concerns	No

Code feedback:

[github-actions]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	Consider refactoring or integrating the conflict checking functionality instead of removing it The removal of the check_conflicts method and related ExecutionConflicts and ExecutionConflictsBuilder types might lead to potential issues if conflict checking between executions is still required elsewhere in the codebase. If the functionality is still needed, consider refactoring or integrating it into other parts of the system rather than removing it entirely. src/eth/primitives/execution.rs [18-19] --use crate::eth::primitives::ExecutionConflicts; --use crate::eth::primitives::ExecutionConflictsBuilder; +use crate::eth::primitives::ExecutionConflicts; +use crate::eth::primitives::ExecutionConflictsBuilder; +// Refactor or integrate conflict checking logic as necessary Suggestion importance[1-10]: 7 Why: The suggestion correctly identifies the removal of significant functionality related to conflict checking between executions. It provides a valid concern about the potential need for this functionality elsewhere in the codebase, suggesting a thoughtful approach to refactoring or integration rather than outright removal.	7