Football - add/expose Point Breakdowns on Player/BoxPlayer

[jessedp]

problem: Currently you can access BoxPlayer.stats[].breakdown and projected_breakdown , but that's awkward and they are the real-world stats (# of yards, # of attempts) not fantasy stats (ppr, points per yardage bucket). The points breakdown also were not accessible via Player.

fix: add points_breakdown and projected_points_breakdown to Player.stats; make breakdown, points_breakdown, projected_breakdown, projected_points_breakdown top level attributes on BoxPlayer. Would have like to just make BoxPlayer.stats = Player.stats, but don't want to break backwards compatibility.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.26%. Comparing base (02fec55) to head (e8349ba).
⚠️ Report is 8 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #665      +/-   ##
==========================================
+ Coverage   71.19%   71.26%   +0.06%     
==========================================
  Files          62       62              
  Lines        2368     2373       +5     
==========================================
+ Hits         1686     1691       +5     
  Misses        682      682              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[jessedp]

This may be similar to or help with what #656 is trying to do? Or maybe they didn't get to the statSourceId check and "dynamic" field layout in player.py?
Note that the functional test I've provided is pulling the test league from 2019 (which I might add test data from).