test: added more code coverage for usecase package

[emeeker2002]

added more code coverage for usecase package

[codecov]

Codecov Report

Attention: Patch coverage is 73.19588% with 26 lines in your changes missing coverage. Please review.

Project coverage is 72.41%. Comparing base (0cb4bdb) to head (cb53d65).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/usecase/devices/interceptor.go	73.19%	18 Missing and 8 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #342      +/-   ##
==========================================
+ Coverage   68.61%   72.41%   +3.80%     
==========================================
  Files          64       64              
  Lines        4320     4376      +56     
==========================================
+ Hits         2964     3169     +205     
+ Misses       1111      949     -162     
- Partials      245      258      +13     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rsdmike]

Looking good Ethan, my only ask is if we can add bounds checking to the overflow errors. Our security folks won't like us ignoring possible overflow integer errors.
I'm thinking we can do something like:

	lenChallengeUsername := uint8(0)
	lenAuthURL := uint8(0)
	// Check for potential overflow
	if len(challenge.Username) <= math.MaxUint8 {
		lenChallengeUsername = uint8(len(challenge.Username))
	}

	if len(authURL) <= math.MaxUint8 {
		lenChallengeUsername = uint8(len(challenge.Username))
	}

That seems to be a way to address the findings: securego/gosec#1187 . It may not get rid of the errors since that was merged so recently, but at least can get the code in place.