Use a single crate/implementation for handling hex-encoding/decoding

[Fraser999]

We currently have a mixture of hand-rolled encoders and usage of the hex crate.

We should check the performance of hex-conservative and use it exclusively throughout our codebase if it's performant enough, or if not, we should just avoid using any third-party crates for this and extend our own hand-rolled implementation to cover all our needs.

Ensure that when using this to display a byte array we make use of appropriate non-allocating functionality provided by hex-conservative crate.

Relevant code paths in this repo:

• astria-telemetry:

  astria/crates/astria-telemetry/src/display.rs

  Lines 59 to 79 in 4478cb6

  	pub fn hex<T: AsRef<[u8]>>(bytes: T) -> Hex<T> {
  	Hex(bytes)
  	}
  	/// A newtype wrapper of a byte slice that implements [`std::fmt::Display`].
  	///
  	/// To be used in tracing contexts. See the [`self::hex`] utility.
  	#[derive(SerializeDisplay)]
  	pub struct Hex<T>(T);
  	impl<T> Display for Hex<T>
  	where
  	T: AsRef<[u8]>,
  	{
  	fn fmt(&self, f: &mut Formatter<'_>) -> Result {
  	for byte in self.0.as_ref() {
  	f.write_fmt(format_args!("{byte:02x}"))?;
  	}
  	Ok(())
  	}
  	}

• astria-sequencer (will be removed with chore(sequencer)!: put blocks and deposits to non-verified storage (ENG-812) #1525):

  astria/crates/astria-sequencer/src/utils.rs

  Lines 16 to 25 in e945677

  	pub(crate) struct Hex<'a>(pub(crate) &'a [u8]);
  	impl<'a> std::fmt::Display for Hex<'a> {
  	fn fmt(&self, f: &mut std::fmt::Formatter<'_>) -> std::fmt::Result {
  	for byte in self.0 {
  	f.write_fmt(format_args!("{byte:02x}"))?;
  	}
  	Ok(())
  	}
  	}

┆Issue Number: ENG-841

[joroshiba]

This issue is stale because it has been open 45 days with no activity. Remove stale label or this issue
be closed in 7 days.