fix(storage): resolve strict linter and TypeScript errors

[thiyaguk09]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• Ensure the tests and linter pass
• Code coverage does not decrease (if any source code was changed)
• Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

[gemini-code-assist]

Code Review

This pull request refactors imports, formatting, and promise handling across several files, and updates tsconfig.json to include more test paths. However, several changes to promise chains (specifically refactoring .then(..., callback) to .then(...).catch(callback) or adding .catch() handlers) introduce critical bugs where callbacks can be invoked twice if the success callback throws an error. These issues affect getProjectId in service.ts, prepareRequest in util.ts, and createURI / createURIAsync in resumable-upload.ts.

[Dhriti07]

We are adding a few "// eslint-disable-next-line @typescript-eslint/no-explicit-any" comments especially in the test files to bypass the new linting rules. While this does work as a quick fix, it might be better to take this as an opportunity to remove the any casts wherever possible

[thiyaguk09]

removed the any casts and the eslint-disable

[Dhriti07]

Thanks for the fixes, I took a look at the PR and still see a few eslint-diable comments lingering. Could we also address those ?