Eliminate Usage of any Types and Enforce the Relevant Rule

[ygrishajev]

We are currently using the any type in several places within our codebase, which is recognized as a suboptimal practice for maintaining type safety. Our existing ESLint configuration flags this as a warning under the rule @typescript-eslint/no-explicit-any: "warn". The objective of this task is to address all occurrences where the any type is used, replace them with more specific type annotations, and enhance our type-checking rigor.

Goals

1. Identify all instances in the codebase where the any type is used.
2. Refactor these instances to use specific and appropriate TypeScript types.
3. Update the ESLint rule @typescript-eslint/no-explicit-any from "warn" to "error" to prevent future use of the any type.

Expected Outcome

The codebase is free from the any type, ensuring higher type safety and compliance with TypeScript best practices. The ESLint rule override is removed, making the no-explicit-any rule an error-level directive.