Feat: Add bundle size tracking and reduce ESLint warnings

[ustaxs]

Summary

This PR introduces two major improvements to our CI process and code quality standards: a new bundle size tracking system and the initial phase of a progressive reduction in ESLint warnings.
Closes #658

Closes #659

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Chore / Refactor (no functional changes)

Testing Done

• Unit Tests
• Integration Tests
• Manual Verification (e.g., iOS/Android UI checks)

Security Considerations

• Does this store user data securely (e.g., avoiding plain AsyncStorage for sensitive data)?
• Is token handling secure (no token exposure in logs or UI)?
• Are all user inputs validated?
• Is deep link handling safe from malicious payloads?

Performance Considerations

• Are React hooks (useCallback, useMemo) used appropriately to prevent unnecessary renders?
• Is FlatList optimized (e.g., using getItemLayout, keyExtractor)?
• Are asynchronous patterns handled correctly (e.g., useEffect cleanup to avoid memory leaks)?
• Have bundle size impacts been considered?

Checklist

• I have read the CONTRIBUTING guide.
• My code follows the style guidelines of this project.
• I have updated the documentation accordingly.
• Are there architectural changes? If so, is there an Architectural Decision Record (ADR)?

[drips-wave]

@ustaxs Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[RUKAYAT-CODER]

Thank you for contributing to the project