refactor(earn): break pool info screen into multiple files

[satish-ravi]

Description

EarnPoolInfoScreen is too big and has too many internal components, this breaks them into multiple files. Also organized all pool info screen files in a sub folder, as the number of files under src/earn was also increasing

Test plan

CI, no visual changes

Related issues

• N/A

Backwards compatibility

Yes

Network scalability

N/A

[codecov]

Codecov Report

Attention: Patch coverage is 99.21875% with 1 line in your changes missing coverage. Please review.

Project coverage is 88.87%. Comparing base (6e03eb4) to head (a3b06f5).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/earn/poolInfoScreen/Cards.tsx	99.08%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##             main    #6176    +/-   ##
========================================
  Coverage   88.86%   88.87%            
========================================
  Files         728      730     +2     
  Lines       30997    31024    +27     
  Branches     5689     5386   -303     
========================================
+ Hits        27546    27573    +27     
- Misses       3255     3409   +154     
+ Partials      196       42   -154     

Files with missing lines	Coverage Δ
...c/earn/poolInfoScreen/BeforeDepositBottomSheet.tsx	100.00% <ø> (ø)
src/earn/poolInfoScreen/EarnPoolInfoScreen.tsx	93.52% <100.00%> (ø)
src/earn/poolInfoScreen/SafetyCard.tsx	100.00% <100.00%> (ø)
src/earn/poolInfoScreen/TokenIcons.tsx	100.00% <100.00%> (ø)
src/earn/poolInfoScreen/Cards.tsx	99.08% <99.08%> (ø)

... and 65 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6e03eb4...a3b06f5. Read the comment docs.

[jh2oman]

Optional nit: I feel like the InfoBottomSheet would be a good candidate to move out into its own file. It probably should be its own generalized file in components, but one step at a time.

[satish-ravi]

yeah I thought about it too, I guess it can be it's own component within earn for now, don't want to generalize too much until it's reused in multiple places and inevitably end up with a component with multiple flags, each just for one use case.