chore(sonar): unexpected any specify a different type

[fernandatoledo]

What does this do?

There's a rule that sonar is applying but we didn't have configured on our Eslint: The "any" type should not be used

Why did you do this?

So that this issues don't come up on sonar anymore.

Who/what does this impact?

Dev experience

How did you test this?

Linting locally

[github-actions]

💯 Test Coverage

Lines	Statements	Branches	Functions
	50.09% (251/501)	41.59% (94/226)	35.93% (69/192)

😎 Tests Results

Tests	Skipped	Failures	Errors	Time
62	0 💤	0 ❌	0 🔥	27.154s ⏱️

👀 Tests Details • (51%)

File	% Stmts	% Branch	% Funcs	% Lines	Uncovered Line #s
All files	50.09	41.59	35.93	51.14
api/common	81.81	50	62.5	85.36
axios.d.ts	0	0	0	0
utils.tsx	84.37	43.75	54.54	89.65	14–20
core	48.14	0	33.33	54.16
utils.ts	60	0	20	85.71	5
core/i18n	63.33	41.17	66.66	62.06
types.ts	0	0	0	0
utils.tsx	56	33.33	66.66	54.16	32, 38–43, 48–60