chore: re-pin crunchy to 0.2.2 after weekly cargo update

[kevaundray]

cargo update is ran weekly however it keeps updating crunchy from 0.2.2 to 0.2.3 even though it should not.

I have not checked the reason for this overriding -- just putting up this PR as a quick hotfix, so that we don't need to do it manually each time.

[kevaundray]

Tested here using a workflow dispatch

[kevaundray]

Leaving this in draft incase its not wanted -- it essentially only saves you one extra commit per week

[mattsse]

let's see how this goes,
tired of doing this manually -.-

[DaniPopes]

This is not the right fix. This pin is present in the root Cargo.toml:

reth/Cargo.toml

Lines 645 to 649 in 76633a5

	# TODO: When we build for a windows target on an ubuntu runner, crunchy tries to
	# get the wrong path, update this when the workflow has been updated
	#
	# See: https://github.com/eira-fransham/crunchy/issues/13
	crunchy = "=0.2.2"

, but it's not included in any of the crates, so it's not applied. Please revert this and add it to one of the workspace crates.

[kevaundray]

This is not the right fix. This pin is present in the root Cargo.toml:

reth/Cargo.toml

Lines 645 to 649 in 76633a5

	# TODO: When we build for a windows target on an ubuntu runner, crunchy tries to
	# get the wrong path, update this when the workflow has been updated
	#
	# See: https://github.com/eira-fransham/crunchy/issues/13
	crunchy = "=0.2.2"

, but it's not included in any of the crates, so it's not applied. Please revert this and add it to one of the workspace crates.

Will revert and check -- I had always assumed that the workspace crate would be respected