fix: correctly decode jwt keys

[klkvr]

Motivation

This currently breaks fusaka-devnet-1

Solution

PR Checklist

• Added Tests
• Added Documentation
• Breaking changes

[graphite-app]

There's a potential issue with the assertion sequence. The first assertion uses secret_0.as_ref().unwrap().clone(), but then the second assertion uses secret_0.unwrap(), which would consume the Result value. This creates a "use after move" situation.

Consider either:

1. Unwrapping all values first:

let unwrapped_0 = secret_0.unwrap();
let unwrapped_1 = secret_1.unwrap();
let unwrapped_2 = secret_2.unwrap();
assert_eq!(unwrapped_0, unwrapped_1);
assert_eq!(unwrapped_0, unwrapped_2);

2. Or cloning before unwrapping in the first assertion:

assert_eq!(secret_0.clone().unwrap(), secret_1.unwrap());
assert_eq!(secret_0.unwrap(), secret_2.unwrap());

Either approach would prevent the move issue while maintaining the test's intent.

Suggested change

	assert_eq!(secret_0.as_ref().unwrap().clone(), secret_1.unwrap());
	assert_eq!(secret_0.unwrap(), secret_2.unwrap());
	let unwrapped_0 = secret_0.unwrap();
	let unwrapped_1 = secret_1.unwrap();
	let unwrapped_2 = secret_2.unwrap();
	assert_eq!(unwrapped_0, unwrapped_1);
	assert_eq!(unwrapped_0, unwrapped_2);

Spotted by Diamond

Is this helpful? React 👍 or 👎 to let us know.

[mattsse]

makes sense