chore: fix lint errors

[rodrodros]

Fixing linting errors

[codecov]

Codecov Report

❌ Patch coverage is 70.00000% with 3 lines in your changes missing coverage. Please review.
✅ Project coverage is 76.19%. Comparing base (646ef43) to head (bef843d).
⚠️ Report is 3 commits behind head on main.

Files with missing lines	Patch %	Lines
core/trie/bitarray.go	0.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3369      +/-   ##
==========================================
- Coverage   76.25%   76.19%   -0.07%     
==========================================
  Files         351      351              
  Lines       33340    33365      +25     
==========================================
- Hits        25423    25422       -1     
- Misses       6103     6131      +28     
+ Partials     1814     1812       -2     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[EgeCaner]

We can initialize the slices with size and assign by index, but I'm not sure if it worth doing since all those are test code and difference should be negligible.

[EgeCaner]

Suggested change

	// 1 byte to accomoaate the length and the other 32 for the data
	// 1 byte to accommodate the length and the other 32 for the data

[MaksymMalicki]

turbo small nit: I'd rename amount to something like numKeys

[rodrodros]

We can initialize the slices with size and assign by index, but I'm not sure if it worth doing since all those are test code and difference should be negligible.

There were some cases where it was not trivial so I decided to leave it as it is (unless trivial) in the test code. I did change all production code that would benefit from this.