BUG: Type Safety: Replace `any` types with proper TypeScript types

### Is there an existing issue for this?

- [x] I have searched the existing issues

### What happened?

**Impact:** Medium - Code quality, maintainability, type safety
**Effort:** Low-Medium (6 occurrences)

Using `any` bypasses TypeScript's type checking, defeating its core purpose.

**Locations:**
- Album.ts:85 - `data: any | null` → Type based on API response
- useQueryExtension.ts:56 - `error: any` → `Error` or `unknown`
- useToggleFav.ts:15 - `id: any` → `string` or `number`
- Sortimage.ts:12 - `data: any` (x2) → Proper image interface
- Icons.tsx:1 - `props: any` (x3) → `React.SVGProps`
- folders.ts:80 - `as any` cast → Already typed as `FolderTaggingInfo[]`

**Benefits:**
- Catch bugs at compile-time vs runtime
- Better IDE autocomplete
- Safer refactoring
- Prevents type juggling vulnerabilities

### Record

- [x] I agree to follow this project's Code of Conduct